** Attachment added: Screenshot-Failed to unmount partitions.png
http://launchpadlibrarian.net/9000201/Screenshot-Failed%20to%20unmount%20partitions.png
--
[gutsy tribe-5] Failed to unmount partitions
https://bugs.launchpad.net/bugs/134883
You received this bug notification because you are
Public bug reported:
Binary package hint: ubiquity
Tribe-5 desktop CD boots successfully on my desktop computer with
ATI9550 graphics card as always. However, X can easily lock up unless
Desktop Effects is disabled as soon as the desktop CD finishes booting.
I am wondering if compiz compositing
Is there a boot option to disable Desktop Effects of the Desktop CD?
--
compiz compositing locks up computer
https://bugs.launchpad.net/bugs/134893
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I am experiencing a similar problem with my HP Compaq 6515b. The
graphics card is an ATI x1270. I cannot get X running. Attaching
Xorg.0.log...
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/9000542/Xorg.0.log
--
desktop cd fails to start gdm with hp nc6400 (widescreen,
using gutsy tribe-5 desktop CD.
--
desktop cd fails to start gdm with hp nc6400 (widescreen, ati-based laptop)
https://bugs.launchpad.net/bugs/103945
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
As of now I am running Feisty for most of the time. I can only upload a
copy of Xorg.0.log before freezes occur. But I am sure that Dapper will
freeze given enough running time, because the button artifacts still
appear.
** Attachment added: Xorg.0.log
How is this solved, by fixing Ubiquity or by patching e2fsck to allow
for 12 hours' time error? I don't think the latter is the right
solution.
--
problem with time
https://bugs.launchpad.net/bugs/89069
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Experiencing exactly the same problem here as what Elmer van Baal
described.
** Changed in: gnome-app-install (Ubuntu)
Status: New = Confirmed
--
gnome-app-install crashed with NameError in preRun()
https://bugs.launchpad.net/bugs/129485
You received this bug notification because you are
I guess this problem shall be seen on all low DPI (96) monitors.
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Setting layout.css.dpi to 0 (rather than -1) seems to fix the problem.
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
No, 1.4.7-1ubuntu1 didn't fix the problem.
Steps to reproduce: Open gnome-terminal, press Ctrl-Shift-T
consecutively for 5 times, without pausing between keystrokes.
--
scim input freezes in various applications
https://bugs.launchpad.net/bugs/66104
You received this bug notification because
I have a workaround for this problem: setting the Gnome DPI to 96,
which was 86 as probed by X. After increasing the DPI parameter, I get
normal font size in firefox rendered web pages, with the side effect
that fonts in other places are universally enlarged.
Workaround:
Right click on desktop
The gtk+2.0 bug fix release (2.11.4-0ubuntu1) for bug #114498 doesn't
fix the problem at all. Please be aware that I reported this bug after
the release of the gtk2 bug fix. Unmarking duplicate...
** This bug is no longer a duplicate of bug 114498
GTK font selection minimum size is too large
I have just compared the panel font sizes in feisty and gutsy, and found
they are of exactly the same size. Therefore, I don't think this bug is
a duplicate of bug #118745.
** This bug is no longer a duplicate of bug 118745
Font sizes in Gutsy are vulnerable to bad X.org DPI detection
**
** Attachment added: Gutsy Desktop screenshot
http://launchpadlibrarian.net/8298464/Desktop-Gutsy.png
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: Feisty Desktop screenshot
http://launchpadlibrarian.net/8298467/Desktop-feisty.png
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Marking it confirmed as it has been confirmed by Ming Hua. With the
default scim config (/FrontEnd/X11/Dynamic = false), keyboard input
locks up much more often in Gutsy than in previous releases. Please
raise the bug importance.
** Changed in: scim (Ubuntu)
Status: New = Confirmed
--
** Changed in: scim (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
--
scim input freezes in various applications
https://bugs.launchpad.net/bugs/66104
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
But changing /FrontEnd/X11/Dynamic to true can still get rid of the
more frequent and more easily reproducible lockups in Gutsy. If the
option is false, keyboard input locks up so frequently as to make the
Gutsy desktop barely usable, and I have to resize/minimize windows in
order to restore
I believe eject is the expected functionality of an external USB drive.
The solution should be to make eject work well with all USB hard drives,
and to make gnome-volume-manager aware of ejects, instead of disabling
eject.
Based on the observation that eject works well with those Cyrpress-based
*** This bug is a duplicate of bug 118745 ***
https://bugs.launchpad.net/bugs/118745
I agree that it may not be a mozilla bug. But in my case, X server
correctly detected the DPI of the screen, which is a 19 LCD
(1280x1024),
(--) RADEON(0): Display dimensions: (380, 300) mm
(--) RADEON(0):
Bug still seen in Gutsy Tribe-2, and Ming Hua's workaround still works.
--
scim input freezes in various applications
https://bugs.launchpad.net/bugs/66104
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I don't think bug #89069 is a duplicate of this bug. Bug #89069 is
clearly a bug in Ubiquity, which updates the system clock to localtime
by syncing to a time server shortly after starting its real installation
work, but without updating the timezone accordingly. It is experienced
by people in GMT
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Still seen in Gutsy Tribe-2 CD.
Proposed bug fix:
If system time has successfully synchronized to a time server, Ubiquity should
leave the timezone setting alone.
If not, Ubiquity should offer users a chance
Public bug reported:
Just reinstalled Gutsy using the Tribe-2 desktop CD. The installation
process is smooth except for the partman halting problem mentioned in
the release notes.
Gutsy boot process halted at the following console error message:
** Attachment added: smaller english fonts in gutsy
http://launchpadlibrarian.net/8175309/gutsy_startpage.png
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Attachment added: normal sized english fonts in feisty
http://launchpadlibrarian.net/8175310/feisty_startpage.png
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which
yes, using Take Screenshot utility. Everything is default except the
/etc/fonts/local.conf. You consider the gutsy start page better probably
only because it is not anti-aliased. But the font size is indeed smaller
in Gutsy. Although smaller English fonts are possibly acceptable, it's
not the
** Attachment added: normal sized chinese fonts in feisty
http://launchpadlibrarian.net/8160028/firefox_feisty.png
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: smaller chinese fonts in gutsy
http://launchpadlibrarian.net/8160006/firefox_gutsy_small_chinese_fonts.png
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you are a member of Ubuntu
I have the attached local.conf for fontconfig in both feisty and gutsy.
** Attachment added: local.conf
http://launchpadlibrarian.net/8160039/local.conf
--
firefox displays fonts smaller than it should have
https://bugs.launchpad.net/bugs/120811
You received this bug notification because you
I can confirm exactly the same problem as described in bug #121092. The
only NIC in my desktop is named eth2, while eth0 and eth1 are for two
none-existent e1000 cards. Attaching 70-persistent-net.rules...
** Attachment added: 70-persistent-net.rules
Public bug reported:
Binary package hint: udev
25-iftab.rules is missing from Gutsy applied with latest updates as of
now. Changing interface name in /etc/iftab no longer works as expected.
Version: 111-0ubuntu4
** Affects: udev (Ubuntu)
Importance: Undecided
Status: Unconfirmed
Public bug reported:
Binary package hint: mozilla-firefox
Using latest version in gutsy. firefox displays fonts a tad too smaller
than it should have, which makes Chinese fonts look jagged and hard to
read. Font size in firefox menu or other applications is normal.
** Affects: firefox (Ubuntu)
Quoting Sitsofe Wheeler [EMAIL PROTECTED]:
Wenzhuo:
It does look like a move to libata is ultimately on the cards. See
http://lwn.net/Articles/198344/ and
http://kernelnewbies.org/Linux_2_6_19#head-cdcbaa9c1b476decdc064e0a75d23d1328b1ddce
for reasons why the change is
happening...
Considering that SATA isn't available on ICH4, and libata is problematic
with usb-storage, please revert to piix for ICH4 variants.
PCI_DEVICE_ID_INTEL_82801DB_10 (0x24ca) is handled by piix in the
vanilla kernel.
--
feisty doesn't work with external CD writers anymore
piix has been handling ICH4 very well for years. no need to switch to
ata_piix, absolutely.
--
feisty doesn't work with external CD writers anymore
https://bugs.launchpad.net/bugs/109211
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Workaround:
1. Add the following to /etc/initramfs-tools/modules
piix
ide-disk
ide-cd
ide-generic
2. update-initramfs -u as root
3. Reboot.
Can someone please confirm the bug?
$ lspci
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev
03)
00:01.0 PCI bridge:
One user who experienced the same problem posted on the ubuntu-users mailing
list:
https://lists.ubuntu.com/archives/ubuntu-users/2007-June/116096.html
His setup is SATA and SCSI combination. But I think the root cause is
the same.
Considering gutsy has already reached alpha milestone, can
Still exists in Gutsy tribe 1.
--
Some chinese character antialiased, some not
https://bugs.launchpad.net/bugs/70041
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
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Gutsy tribe 1 still has the problem. I think this bug is not a duplicate
of bug #63175. This bug is the result of a bug in the installer, whereas
bug #63175 is probably not.
--
problem with time
bug fixed in 2.6.20-16.28. Clearly, it is caused by libata.
--
feisty doesn't work with external CD writers anymore
https://bugs.launchpad.net/bugs/109211
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
2.6.20-16.29 reintroduced the bug.
--
feisty doesn't work with external CD writers anymore
https://bugs.launchpad.net/bugs/109211
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 should be more cautious in choosing between libata and the gold
old ide drivers.
--
feisty doesn't work with external CD writers anymore
https://bugs.launchpad.net/bugs/109211
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Dapper, with latest updates, still hangs when dosfsck'ing a FAT32
partition with such a big file in it. Please backport the bug fix to
dapper. Thanks
--
fsck.vfat truncates files of 4294967295 bytes length to 0 bytes at boot-time
https://bugs.launchpad.net/bugs/62831
You received this bug
Onno Benschop, please be aware that the bug was filed against sysvinit,
instead of dosfstools. There is no point for Ubuntu to check FAT32
partitions in the first place, especially when dosfsck is buggy.
I am affected by the dosfsck bug #62831 as well. The file got truncated
by dosfsck is (4G-1)
drives (the previously described CDR/RW and a
CDRom drive), I tried putting one of my ubuntu cds in the drives to see what
happens. The CD mounts in the CDRom drive, but fails to do so in the external
drive. I don't know if that is also happening to Wenzhuo Zhang, since he did
not say
After installing the hal update (0.5.9-1ubuntu2~feisty1) released
several days ago, eject becomes unmount on the context menu for USB hard
drives. I think It is a workaround for this problem, but it's not a nice
solution.
--
do not eject all USB/Firewire devices
Just for the record: among the three external hard drives I have access
to, feisty can eject two Cypress CY7C68300C-56PVXC based external hard
drives smoothly; it cannot eject the one based on Initio INIC-1530L.
Perhaps it is a bug in the usb_storage driver?
I hope the problem will be fixed soon.
J wrote:
This is *very* probably a HAL bug, if you can mount/unmont the thing, it
means the kernel driver and udev is working properly, as the device node
is created. Can you please try with the above (
https://bugs.launchpad.net/ubuntu/+source/gnome-volume-
manager/+bug/63090/comments/33 )
dmesg output when inserting and ejecting an USB external harddrive. It
is a Zynet Monster 3 IN 1 Data Center, which is a USB 2.0 Hub + Flash
Card Readers + USB hard drive combo. The USB/Firewire - IDE adapter
included in this device is produced by Initio. Ejecting the external
hard drive used to
** Attachment added: lsusb output of Zynet Monster 3 IN 1 Data Center
http://librarian.launchpad.net/7411094/lsusb.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Feisty can eject this external hard drive well.
** Attachment added: lsusb output of Zynet HD-D13-U2 hard drive enclosure
http://librarian.launchpad.net/743/Zynet-HD-D13-U2.lsusb.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug
Lionel Patoureau wrote:
I had the same problem with Mandriva 10, but I solved it when I set the
boot sequence by loading first the hd in the Promise ide controller as
well as I installed grub or lilo on that same hd. Not on the master of
the motherboard's ide controller.
I solved it by fist
Yes, this is onboard audio controller that comes with intel i855
chipset. The computer is a ThinkPad X32 laptop. You can use lspci -v
to list your PCI device information.
--
Microphone Not Working In Feisty 7.04
https://bugs.launchpad.net/bugs/108828
You received this bug notification because
Adding another sound card, which used to work well in Edgy:
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
Subsystem: IBM Unknown device 0534
Flags: bus master, medium devsel, latency 0, IRQ 11
Public bug reported:
Binary package hint: nautilus-cd-burner
It seems that feisty doesn't work with external CD writers anymore. I
have tried two external USB CD writers: 1. TEAC DW-224E-B 1.6A; 2.
Samsung CD-RW/DVD Drive SM-348 + USB - IDE adapter. Those same CD
writers work well with dapper
** Attachment added: Insert a blank disc prompt
http://librarian.launchpad.net/7390414/Screenshot-nautilus-cd-burner.png
--
feisty doesn't work with external CD writers anymore
https://bugs.launchpad.net/bugs/109211
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: XE310-dmesg.correct_hd_order.log
http://librarian.launchpad.net/7390545/XE310-dmesg.correct_hd_order.log
--
newly installed feisty unbootable on desktops with harddrives connected to
add-on PCI IDE controller card
https://bugs.launchpad.net/bugs/109218
You received this
Public bug reported:
I tried to install feisty RC several days before its final release on an
old desktop computer. After seemingly smooth and successful
installation, the computer could not load Grub because it had been
installed on the tertiary master hard drive connected to an add-on PCI
IDE
** Attachment added: XE310-lspci-v.correct_hd_order.log
http://librarian.launchpad.net/7390549/XE310-lspci-v.correct_hd_order.log
--
newly installed feisty unbootable on desktops with harddrives connected to
add-on PCI IDE controller card
https://bugs.launchpad.net/bugs/109218
You received
Just for the record: I have reported bug #109211 for the external CD writer
problem, and bug #109218 for the device ordering problem.
https://bugs.launchpad.net/ubuntu/+bug/109211
https://bugs.launchpad.net/ubuntu/+bug/109218
Wenzhuo Zhang wrote:
I am testing the desktop-i386 image on an old
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Matt Zimmerman wrote:
OK, this was the missing bit of information. This problem is specific to
the situation where your hardware clock is set to local time. Depending on
and specific to users in GMT +
*** This bug is a duplicate of bug 84899 ***
https://bugs.launchpad.net/bugs/84899
Ryan wrote:
*** This bug is a duplicate of bug 84899 ***
https://bugs.launchpad.net/bugs/84899
The change fixes the delay, and it is odd that it was set to yes in the
default ubuntu config since the
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Patrice, are you sure your hardware clock was set to UTC time? By
default, Windows XP presumes that the hardware clock is in local time.
--
problem with time
https://bugs.launchpad.net/bugs/89069
You received
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Steps to reproduce:
Suppose the current time is 9:00 GMT, and you're in Shanghai, and your
computer is connected to the Internet:
1. Enter BIOS and set RTC to 17:00, which is China Standard time
GMT+800.
2.
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Proposed fix 2: Ubiquity can also set the system clock from the RTC
using the chosen timezone. But it must offer users a chance at the same
time to specify whether the RTC is in UTC.
--
problem with time
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
Assume you are currently in China, and the hardware clock of your
computer is set to Beijing time (GMT+800) to accommodate the requirement
of Windows. After booting the feisty desktop-i386 CD, the system clock
Matthew Garrett wrote:
No, I don't think that the ordering of devices is a bug - the bug is
that we're assuming that the Linux device ordering bears some sort of
relation to the Bios device ordering, which is simply not true. Further,
Perhaps it is not a bug as far as the kernel is
After some researching, I think it must be caused by the fact that the
hwclock.sh init script gets run very late in the boot process. Priror to
S50hwclock.sh, the system clock (or kernel clock) is uninitialized, so
fsck-1.40 complains the last mount/write time is in the future.
--
Edgy Beta --
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
I think I have located the root cause of the problem. Ubiquity updates
the system clock to local time without changing the timezone accordingly,
which causes the last mount/write time 8 hours ahead in my case.
If I were not wrong, this problem shall be experienced by people living
in the GMT minus timezones who reboots often. The root cause of this
problem is that the kernel initializes the system clock from the RTC,
the hardware clock on motherboard, which is several hours behind UTC in
GMT minus
*** This bug is a duplicate of bug 63175 ***
https://bugs.launchpad.net/bugs/63175
I am still seeing this problem on feisty RC. I live in GMT +8 timezone, and the
hardware clock is set to localtime, because I have Windows installed. I choose
Asia/Shanghai as my timezone in Ubiquity. Upon
Wenzhuo Zhang wrote:
Wenzhuo Zhang wrote:
3. The desktop has two hard drives. One is connected to the motherboard
as primary master, and the other is connected to a Promise Ultra100 TX2
IDE controller card as tertiary master. The feisty live-cd recognizes
the primary boot drive as /dev/sdb
Wenzhuo Zhang wrote:
To obtain dmesg and lspci output for bug reporting, I booted up the feisty
desktop-i386 live-cd again. To my surprise, it correctly recognized the
two hard drives this time. To reconfirm, I rebooted the live-cd, and it
recognized correctly again.
Still, there must
Sorry I missed your post dated 2007-01-10. As I wrote clearly in the bug
description, this was a default edgy install, and broken right
parentheses were seen in window menus and buttons of various
applications.
The problem has been fixed in Feisty beta.
** Attachment added: gnome-terminal in
-15.25 works for me. IDE, Thinkpad x32.
--
MASTER: Computer will not boot after 2.6.20-14.23 kernel upgrade
https://bugs.launchpad.net/bugs/106063
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL
In response to a testing wanted message on the ubuntu-devel list, I sent
a bug report to kernel-team shortly after the kernel upgrades appeared
in the repsository. But the messages are still awaiting moderator
approval as of now. Attached is the result of lspci -vvn. The hardware
is a ThinkPad
Obviously, it's a regression introduced in 0.6.4-6ubuntu5. If I
downgrade to 0.6.4-6ubuntu4, the applet works very well.
# sudo dpkg -i --force-downgrade /var/cache/apt/archives/network-
manager-gnome_0.6.4-6ubuntu4_i386.deb /var/cache/apt/archives/network-
manager_0.6.4-6ubuntu4_i386.deb
--
Another problem with 0.6.4-6ubuntu6: if I right click the applet icon
and de-select Enable Wireless, the applet silently quits.
--
Netowrk manager says disconnected but is connected and working
https://bugs.launchpad.net/bugs/105234
You received this bug notification because you are a member of
After commenting out the static parameters (address, network and
gateway) of the primary network interface stanza in my
http://librarian.launchpad.net/7259051/interfaces, 0.6.4-ubuntu6 works
again, and it no longer quits silently when disabling wireless.
--
Netowrk manager says disconnected but
My previous comment https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/105234/comments/53 is wrong. network-manager-0.6.4-ubuntu6
works OK only after freshly upgraded from 0.6.4-ubuntu4. But, after
restarting Gnome, network-manager-0.6.4-ubuntu6 still shows no network
connection, even
I am afraid 0.6.4-6ubuntu6 does not fix the problem on my laptop. I have
restarted Gnome.
--
Netowrk manager says disconnected but is connected and working
https://bugs.launchpad.net/bugs/105234
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Public bug reported:
Binary package hint: network-manager
The network-manager update released yesterday, 0.6.4-6ubuntu5, is not
working properly on my ThinkPad X32 with one wired network connection
and one wireless. Its applet icon shows No network connection,
although Static configuration...
** Attachment added: interfaces
http://librarian.launchpad.net/7259051/interfaces
--
network-manager-0.6.4-6ubuntu5 No network connection
https://bugs.launchpad.net/bugs/105343
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
parted-1.8.6 also failed when copying the bigger partition (/dev/hde6).
It failed with the same error messages, but without the detailed help
information. On the contrary to my assumption, the ext3 resizing code of
GNU parted is still EXPERIMENTAL, as it warns in interactive mode. I was
too quick
well, I think parted should not try to resize ext3 partitions when its
code is still experimental. Even when it's beta quality, it should
provide an option to disable automatic filesystem resizing.
--
Parted assertion failure
https://bugs.launchpad.net/bugs/103533
You received this bug
Public bug reported:
Binary package hint: parted
I bought a new Seagate 320G IDE drive last weekend, and installed it in
my home desktop last night. I booted into the Edgy Desktop CD to create
partitions and to migrate data. Before going to bed last night, I typed
the following command to copy
I just noticed the problem as well. There is about 5 seconds delay when
ssh to a local server. After changing GSSAPIAuthentication yes to
GSSAPIAuthentication no in /etc/ssh/ssh_config, ssh login is almost
instantaneous.
[EMAIL PROTECTED]:~$ ssh -v panda
OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL
panda.zhmail.com, it's a machine on the same LAN as thinkpad. I run
dnscache on thinkpad, and the TTL of panda.zhmail.com is 2 days, and I
put 172.16.10.32 thinkpad in panda:/etc/hosts, so the delay was not
caused by DNS resolving. Considering that the delay occured as ssh
printed out the
I am experiencing exactly the same problem. For details, please read
https://launchpad.net/ubuntu/+bug/69941/comments/7
--
[feisty] Slow gnome application startup due to /etc/hosts misconfiguration
https://launchpad.net/bugs/94048
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can confirm the same problem on feisty beta. Aside from very slow
login, two panel applets, namely CPUFreqApplet and WeatherApplet, would
fail to start, when there is no wired network connection.
The tip in https://launchpad.net/ubuntu/+bug/69941/comments/6 works for
me. Well, I removed the
I have had edgy in another partition since its beta release. It doesn't
freeze. - Well, perhaps it had a lockup or two as well, which might not
be related to the ati driver at all.
--
ThinkPad X32 freezes often after upgrading to dapper
https://launchpad.net/bugs/55570
--
ubuntu-bugs mailing
I guess one character in your screenshot comes from the Japanese font
Kochi Mincho and the other comes from a Chinese font, because Kochi
Mincho comes before the Chinese fonts in the standard aliases (serif,
sans-serif, and mono) of the default font.conf.
I always create /etc/fonts/local.conf,
I can confirm the bug. I spent hours this afternoon trying to configure
a HP LaserJet 1300 (connected to the local parallel port) in Dapper.
Things I did include:
1. Trying the hpijs 0.9.7 driver and the recommended postscript driver.
2. Adding and configuring using the Printing Administration
Public bug reported:
Binary package hint: ubiquity
I just tried to install edgy onto an unformatted partition in a multi-
boot system using the Desktop CD. The GUI installer failed to recognize
the unformatted partition as the root partition, and could not go
forward.
I would not like the GUI
Just tried to configure LaserJet 1300 in Edgy. Although the parport
kernel module correctly recognizes the printer, gnome-cups-manager
cannot detect it, and defaults to the Use another printer by specifying
a port option.
--
hp laserjet 1100 fails to print
https://launchpad.net/bugs/52277
--
Changing affects to linux-source-2.6.17. I wish someone in the Ubuntu
kernel team would notice the bug.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 = linux-source-2.6.17
--
[regression] Suspend [to-RAM and to-disk] is broken in 2.6.15-25.43
I take back my previous comment (#70). Suspend-to-ram is still broken
on ThinkPad X32. What looks bizarre to me is that suspend-to-disk no
longer works reliably as well. The first suspend-to-disk works well. But
later attempts can only yield a dimmed LCD and a password prompt.
Running
Attaching a screenshot of gnome-terminal.
** Attachment added: gnome-terminal in zh_CN.UTF-8
http://librarian.launchpad.net/4890567/gnome-terminal-menu-zh_CN.PNG
--
broken right parenthesis in Chinese locale
https://launchpad.net/bugs/66885
--
ubuntu-bugs mailing list
201 - 300 of 338 matches
Mail list logo
