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 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
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,
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.
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
*** 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
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.
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
*** 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
--
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
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.
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
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
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
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
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
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
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
** 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
** 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.
--
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.
** 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.
--
** 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
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
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
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
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
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
** 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
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
** 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
*** 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
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
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
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
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
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
** 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
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
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
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
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
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
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
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)
** 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.
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
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
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
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
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
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
** 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,
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
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
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.
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
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
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
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
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
** 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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.
--
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
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
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
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
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
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
1 - 100 of 158 matches
Mail list logo
