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
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 w
** 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 passw
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/0
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 subs
>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 opportuni
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 ei
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 li
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.laun
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 4
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
** 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
*** 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
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 Sat
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 not
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 rec
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)
Importance:
** 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 Ubuntu
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 fin
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 new
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://
** 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
** 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, whi
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 u
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 t
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 ar
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.laun
** 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,
** 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.
--
ubun
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.
--
ubun
** 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 subsc
As part of an energy (environment) saving drive, I have migrated to
Ubuntu dapper from sarge on my main machine mainly because there is
better support for suspend and hibernate. Sadly, the (newer) unbranded
keyboards which feature power keys are of poor quality; I can't get on
with them. Many newer
Public bug reported:
Fixing this bug:
https://launchpad.net/distros/ubuntu/+source/control-center/+bug/32126
has created a new bug. There is no way to invoke sleep from a keyboard
shortcut.
I have tried changing keyboards as a result of this bug, but haven't yet
found a power button keyboard I
It is a bug for the desktop infrastructure to handle keyboard events for
suspend and hibernate.
Users of all desktops and users of console will want consistent power
saving keyboard shortcuts.
The desktop environment should just write the settings to a config file
and let a script make changes to
It is a bug for the desktop infrastructure to handle keyboard events for
suspend and hibernate.
Users of all desktops and users of console will want consistent power
saving keyboard shortcuts.
The desktop environment should just write the settings to a config file
and let a script make changes to
Public bug reported:
For dapper:
Fresh install of Dapper. Connect Epson CX5400 to machine, boot machine. Start
Xsane Image Scanner. Hit scan, works.
For Edgy:
Install Edgy. Boot with CX5400 connected. Start Xsane. No device detected.
Troubleshooting:
Dapper:
[EMAIL PROTECTED]:~$ scanimage -L
d
[EMAIL PROTECTED]:~$ export SANE_DEBUG_EPSON=256
[EMAIL PROTECTED]:~$ scanimage -L 2>&1 &>/tmp/edgy-sane-cx5400-debug
** Attachment added: "Debug output from epson backend for CX5400 on Edgy"
http://librarian.launchpad.net/4930646/edgy-sane-cx5400-debug
--
Epson CX5400 not detected in Edgy.
[EMAIL PROTECTED]:~$ export SANE_DEBUG_EPSON=128
[EMAIL PROTECTED]:~$ scanimage -L 2>&1 &>/tmp/edgy-sane-cx5400-debug
** Attachment added: "Debug output from epson backend for CX5400 on Edgy"
http://librarian.launchpad.net/4930645/edgy-sane-cx5400-debug
--
Epson CX5400 not detected in Edgy.
[EMAIL PROTECTED]:~$ export SANE_DEBUG_EPSON=256
[EMAIL PROTECTED]:~$ scanimage -L 2>&1 &>/tmp/dapper-working-sane-cx5400-debug
** Attachment added: "Debug output from *working* epson backend for CX5400 on
Dapper"
http://librarian.launchpad.net/4930647/dapper-working-sane-cx5400-debug
--
Temporary fix:
Grab dapper libsane from:
http://www.mirror.ac.uk/mirror/archive.ubuntu.com/ubuntu/pool/main/s/sane-backends/libsane_1.0.17-1ubuntu4_i386.deb
then as root
dpkg -i sane-backends/libsane_1.0.17-1ubuntu4_i386.deb
Then to prevent the package changing, do
aptitude hold libsane
--
Epso
This bug has been reported upstream as:
http://alioth.debian.org/tracker/index.php?func=detail&aid=304030&group_id=30186&atid=410366
--
Epson CX5400 not detected in Edgy. Works in Dapper.
https://launchpad.net/bugs/67659
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
I am using a d-link WL-107g cardbus adapter connected to an IBM thinkpad
570 (Pentium 2 366). The adapter uses the ralink RT-2500 chipset.
lspci -v:
:06:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference
Card (rev 01)
Subsystem: ASUSTeK Computer Inc.: Unknown devic
Hello Dimitri
I am making the point that whether using an older or newer version of
the kernel, whether 386 or 686, it works for me.
Of course, this doesn't immediately help you if it isn't working for
you. But at least the developer knows that there are platforms where it
works perfectly, and th
Such an indicator would need to activate the laptop screen whilst set to
external output. This would require overriding the laptop interrupt
system, which would be difficult or impossible. Also, such an
implementation if it were possible wouldn't be generic, but specific to
particular models. Also,
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 progress
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 receive
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
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 bo
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 p
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 up
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:B
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 mailin
My experience, which may differ from others, especially Stephan Vanigan,
is that compelling people to upgrade from Windows to Ubuntu causes a lot
of damage.
I have tried strong encouragement and inducement, and found that users
will fall back on me to push them every inch of the way. It is just no
Hello Amir
Perhaps we need to evaluate and consider priorities for R-L language
support, by considering how much an initiative put into improved R-L
support will pay back with increased community contribution.
To bring GNU/Linux to critical mass quickly, it is essential to focus on
areas where we
I have had a similar problem and determined the problem due to the USB driver.
Please see
Bug #128322.
try as root:
rmmod ohci_hcd
to see if the machine then enters suspend.
It may not recover from suspend if using the nv video driver from
another bug I'm just about to file.
--
suspend to r
Public bug reported:
Binary package hint: xserver-xorg-driver-nv
I have noticed various reports referring to the non-free binary drivers
and suspend/resume. Of course, there is not much we can do about that.
This bug report refers solely to the free driver with Xorg. I don't use
non-free binary d
** Attachment added: "nvidia-suspend-debug.tar.gz"
http://launchpadlibrarian.net/8570006/nvidia-suspend-debug.tar.gz
--
nv free driver no display on return from suspend to ram
https://bugs.launchpad.net/bugs/128413
You received this bug notification because you are a member of Ubuntu
Bugs, wh
It appears Gutsy Tribe 2 + fixes this bug.
** Changed in: sane-backends (Ubuntu)
Status: New => Fix Released
** Changed in: sane-backends (Ubuntu)
Status: Fix Released => Fix Committed
--
Epson CX5900 scanner/printer scanner part not detected
https://bugs.launchpad.net/bugs/72506
Kernel version
uname -r
2.6.22-8-386
re-attached hwinfo.tar - Last one doesn't view easily in archive
manager.
** Attachment added: "hwinfo.tar"
http://launchpadlibrarian.net/8579603/hwinfo.tar
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128616
Y
I said:
This functions correctly with a fully updated Gutsy running on a VIA chipset,
which has interrupt 3 assigned
Please ignore that. First col 8 second col 3 on Via.
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128616
You received this bug notific
lspci -v
lshw
cat /proc/interruipts
cat /proc/ioports
dmesg
** Attachment added: "hwinfo.tar.gz"
http://launchpadlibrarian.net/8579113/hwinfo.tar.gz
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128616
You received this bug notification because you
Hello Michael
It appears suspend to ram problems often/usually come from hardware drivers.
To determine where the problem was on my system, I entered the
motherboard BIOS then disabled all non-critical on-board hardware. Re-
enabled hardware one by one so that I could pinpoint which hardware
driv
Hello Andreas
Presumably your fonts scaled to 75dpi but displayed on your 96dpi
screen. They were therefore not displayed as an 11pt font but instead
displayed as an 8.5pt font. Now the dpi is presumably detected
correctly, it is displayed, as set, at 11pt.
As you rightly say, there is a matter o
Hello Sitsofe
The explanation Matthew Garrett gave on bug 121801 looks plausible for this bug.
In these cases, I would mark this bug as a dupe of 121801. However, that bug is:
1) Filed against Vesa driver
2) Filed against a specific model of Nvidia chip where mine covers testing of
two and provid
Procedure:
1) Disable all possible on-board hardware in BIOS (except interface used to
boot from, eg IDE),
2) Reboot machine to see if it enters suspend.
3) If machine enters suspend, you know it is a driver for one of the pieces of
hardware you disabled.
4) If machine still does not suspend, try
lshw > hardware_list.txt
for machine showing this bug.
** Attachment added: "hardware list for sample machine."
http://launchpadlibrarian.net/8567890/hardware_list.txt
--
OHCI_HCD blocks suspend to ram on Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128322
You received this bug notific
I am using the free 'nv' display driver.
[EMAIL PROTECTED]:/home/nick# cat /proc/interrupts
CPU0
0: 2893 IO-APIC-edge timer
1:654 IO-APIC-edge i8042
6: 5 IO-APIC-edge floppy
7: 1 IO-APIC-edge parport0
8:
Public bug reported:
Binary package hint: linux-386
Ubuntu Gutsy.
Nvidia 6100 chipset based motherboard/ AMD Athlon 3200+ CPU, 1G DDR2 RAM.
Enter BIOS. Enable S3 STR.
Boot machine with Ubuntu Gutsy Tribe 3 25/7/07. Kernel (uname -r)
2.6.22-8-386.
Hit sleep button or go System->Quit->Suspend
E
I can confirm this bug.
Expected behaviour:
When logged in, do ctrl+alt+backspace to re-start x-server. When GDM loads,
mouse pointer should be visible.
Actual behaviour
When logged in, do ctrl+alt+backspace to re-start x-server. When GDM loads,
mouse pointer is invisible, but all controls resp
** Changed in: xserver-xorg-driver-nv (Ubuntu)
Sourcepackagename: None => xserver-xorg-driver-nv
** Changed in: xserver-xorg-driver-nv (Ubuntu)
Status: New => Confirmed
--
Mouse Pointer goes invisible after Re-login
https://bugs.launchpad.net/bugs/123389
You received this bug notification
Public bug reported:
Binary package hint: linux-386
Set clock on system eg
#> ntpdate pool.ntp.org
Set hardware clock from system clock
hwclock --systohc
Actual Behaviour:
[EMAIL PROTECTED]:/tmp# hwclock --systohc
select() to /dev/rtc to wait for clock tick timed out
[EMAIL PROTECTED]:/tmp# hw
Hello Matthew
don't know if this helps, but I have provided xorg.0.log outputs for
the 6100 before and after suspend to RAM in my Bug #128413 , after
resume from STR, the computer is responsive, can SSH in, but has no
display. It may be a special situation with this chipset where the
machine is a
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 addre
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://bug
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 sw
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 clea
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 a
Hello Patrice
How did you sett he DPI for your system?
For my 17" TFT monitor, I set screen size and hence DPI in xorg.conf like:
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 30-65
VertRefresh 50-75
DisplayS
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
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
wid
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 f
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 Gu
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/
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.launch
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 resolutio
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 rece
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.
--
u
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 c
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
>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.
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 tried
1 - 100 of 147 matches
Mail list logo
