Public bug reported:
Binary package hint: qemu
On Gutsy 64-bit using qemu/kvm and the -usb switch no USB devices are
available since qemu/kvm looks for them in
/proc/bus/usb/devices
but they are now in
/sys/bus/usb/devices
qemu/kvm reports:
qemuctl -qemu vdeq kvm -boot c -m 512 -hda
** Attachment added: Patch to use /sys/bus/usb
http://launchpadlibrarian.net/10126012/kvm-qemu-usb-linux.diff
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I've got the same problem here. Bluetooth printing to HP Deskjet 995C
was working fine earlier in the Gutsy release cycle but tonight I find
it can't print and the reason appears to be related to the appamor
configuration in /etc/appamor.d/usr.sbin.cupsd since disabling appamor
(sudo
I found a comment that seems strongly related to this in bug #139665 by
Martin Pitt:
https://bugs.edge.launchpad.net/ubuntu/+source/cupsys/+bug/139665/comments/2
Which seems to suggest the issue isn't strictly appamor but cups trying
to access /dev/tty inappropriately.
--
[Gutsy] : bluetooth
Martin's comment about /dev/tty and cupsd seems related to an issue I've
recently experienced and attached a report to bug #147800 ...bluetooth
printing was working but is not...
Disabling appamor provided a work-around in that case but I'd like to
sort the issue out with appamor or cupsd.
--
It is working correctly here for x86_64 with nvidia-glx-new on Nvidia
GeForce Go 7600.
--
GDM Startup Fails With Accessible login
https://bugs.launchpad.net/bugs/107383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I think the issue was caused by bug #143958 that Colin and I solved
earlier in the Gutsy development cycle. A similar issue occurred on a
laptop using the Alternate installer. I'll try to test this out on a
server over the next few days.
--
Feisty LiveCD: Unable to find a medium containing a
It does look as if this bug has returned. I'll dig into it.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
Status: Incomplete = Confirmed
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https
I've been seeing this problem with Alt+Tab and Shift+Alt+Tab for the
last 2-3 weeks of the Gutsy development cycle but only just bothered to
research it. The gconf apps/metacity/global_keybindings/switch_windows*
edits fixed it, although compiz is running by default.
It *may* have been caused by
I was just thinking earlier about how to further debug this. The
problem is still present with the final release updates.
--
gnome-terminal resize legend displayed as blocks when Compiz is enabled
https://bugs.launchpad.net/bugs/145604
You received this bug notification because you are a member
Sometimes it helps to engage brain before putting mouth into gear!
In my edd module-build instructions above I forgot two things:
1. libx86 is for user-space applications; no involvement in the kernel (was
thinking about vbetool at the time I typed that!)
2. The built module can't be modprobe-d
If you're feeling particularly adventurous you could build the kernel
EDD module.
1. Install the kernel-source from GIT
(https://wiki.ubuntu.com/KernelGitGuide) or use
$ sudo apt-get install linux-source
$ sudo tar -xjf linux-source-2.6.22.tar.bz2
$ cd /usr/src/linux-source-2.6.22
2. Edit
A follow-up to my observations of the SCSI address allocation. It looks
as if this is determined in
drivers/ata/libata-core.c::ata_host_register()
where, in part, you find /* print per-port info to dmesg */
and in turn calls
drivers/ata/libata-scsi.c::ata_scsi_scan_host()
It appears that
Mikel, thanks for those reports, they help clarify your circumstances
tremendously. This is just off the top of my head without any real
investigation, but the difference in the SCSI addresses between Windows
and Linux makes me wonder about how the SCSI addressing is being
determined.
For
Will all those experiencing this bug with Gutsy give us detailed
information as to the physical configuration of the motherboard disk
interfaces and disk drives so we can understand the precise
circumstances that cause this?
Right now we have a combination of comments, some of which indicate an
Robert, the solution to your issue is to edit /boot/grub/menu.lst and
set groot correctly. This is what is used when the kernel is updated.
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You
Robert, the entries in menu.lst inside the
### BEGIN AUTOMAGIC KERNELS LIST
section that begin with a single comment # are actually used by the
updater as settings.
Genuine comments use two ## symbols, just to confuse you.
--
grub guessed BIOS disk order incorrectly
** Attachment removed: network-manager-applet_0.6.5.debdiff
http://launchpadlibrarian.net/10171960/network-manager-
applet_0.6.5.debdiff
** Attachment added: Hardy debdiff -0ubuntu11
http://launchpadlibrarian.net/10204380/network-manager-applet_0.6.5-0ubuntu11-hardy.debdiff
--
** Attachment added: Gutsy-proposed debdiff -0ubuntu11
http://launchpadlibrarian.net/10204405/network-manager-applet_0.6.5-0ubuntu11-gutsy.debdiff
--
nm-applet crashed with SIGSEGV in gtk_combo_box_set_model
https://bugs.launchpad.net/bugs/124336
You received this bug notification because
I've created and attached two patches:
1) network-manager-applet (0.6.5-0ubuntu11) hardy; urgency=low
2) network-manager-applet (0.6.5-0ubuntu11) gutsy-proposed; urgency=low
The original packages in Hardy and Gutsy are identical: network-manager-
applet (0.6.5-0ubuntu10) gutsy
The patch solves
** Attachment removed: Patch to use /sys/bus/usb
http://launchpadlibrarian.net/10126012/kvm-qemu-usb-linux.diff
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
aot2002: Just as per the instructions given above. Download and install
the new binary deb.
I don't see any errors reported to the console here.
I've modified the directory layout on my server so there are directories
for each Ubuntu release, so the direct URL is now:
Scott, thanks for the explanation. When I'd re-aimed kvm at
/sys/bus/usb/ I hadn't realised that it looks a for a file 'devices'. I
thought it was looking for the base of a directory-tree containing the
devices, which is what /sys/bus/usb/devices is.
I'm not sure who is primary maintainer at
aot2002: I'm doubtful the error messages you're reporting are caused by
the patch adding a function prototype although it might be caused by the
amd64 .deb package I've built. That said, the build log reports zero (0)
warnings or errors and nm-applet is working without any detectable
problems
** Attachment added: qemu -2ubuntu5 gutsy-proposed debdiff
http://launchpadlibrarian.net/10207775/qemu_0.9.0-2ubuntu5-gutsy.debdiff
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: kvm -4ubuntu3 hardy debdiff
http://launchpadlibrarian.net/10207761/kvm_28-4ubuntu3-hardy.debdiff
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
These patches fix an issue where qemu/kvm expects to find the USB
devices file at /proc/bus/usb/devices and reports an error when started
with the -usb flag as result. The location was changed in July as a
result of a patch to sysvinit and is now /dev/bus/usb/devices.
** Attachment added: qemu
aot2002: I've just looked at your logs and the last time I see the
SIGSEGV is:
Oct 29 08:15:10 localhost kernel: [ 103.908729] nm-applet[6066]:
segfault at ac043cc0
After that I see:
Oct 29 08:21:06 sudo: USER=root ; COMMAND=/usr/bin/killall nm-applet
Oct 29 08:21:45 sudo: USER=root ;
** Changed in: kvm (Ubuntu)
Status: Fix Committed = In Progress
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: qemu (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
Status: Fix Committed = Confirmed
** Changed in: kvm (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
Status: In Progress = Confirmed
--
Could not open /proc/bus/usb/devices
https
** Changed in: network-manager-applet (Ubuntu)
Status: Fix Committed = In Progress
** Changed in: network-manager-applet (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
Status: In Progress = Confirmed
--
nm-applet crashed with SIGSEGV in gtk_combo_box_set_model
https
This is the kind of output to expect from the kvm/qemu debug shell
(easily accessible when using qemuctl). The attachment is a screen-shot
of qemuctl after doing Connect USB Renew.
(qemu) show usbhost
Device 4.2, speed 12 Mb/s
Class e0: USB device 044e:300d, UGX
Device 2.8, speed 480
I'm working with Gutsy and kvm/qemu. I got around this by modifying the
permission rule in
/etc/udev/rules.d/40-permissions.rules
I added GROUP=plugdev so that the USB devices are members of that
group:
# USB devices (usbfs replacement)
SUBSYSTEM==usb_device,MODE=0664,
Assignee: (unassigned) = TJ (intuitivenipple)
Status: New = Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided = Wishlist
Assignee: (unassigned) = TJ (intuitivenipple)
Status: Invalid = Confirmed
--
usb is not available as normal user
https
Wally, you can test it using the Desktop Live CD just as easily.
Once the desktop has started open a terminal and type the commands
listed:
Applications Accessories Terminal
$ wget
http://intuitivenipple.net/dev/ubuntu/gutsy/network-manager-gnome_0.6.5-0ubuntu11_amd64.deb
$ sudo killall
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.6.5-0ubuntu9
PackageArchitecture: amd64
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/tj
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 11
*** This bug is a duplicate of bug 124336 ***
https://bugs.launchpad.net/bugs/124336
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/9511709/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/9511710/Dependencies.txt
** Attachment added:
/bin/nm-applet
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.6.5-0ubuntu9
PackageArchitecture: amd64
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/tj
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_GB.UTF-8
Confirmed. I thought it was my imagination but since an update about a
week ago (so, around 20th September 2007) gnome-power-manager doesn't
hibernate the PC when battery level gets to critical. This had been
working fine up to then and was in regular use.
I did a manual hibernate test from a
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/9512791/Xorg.0.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: xserver-xorg
Gutsy 32-bit LiveCD Beta (20070925.2) on Sony Vaio SRX51P with Intel
i810 video.
When GDM starts the backlight is lit but no display. Able to switch to
VT consoles (which are displayed and are interactive) and back. Using
ps and checking
** Attachment added: kern.log
http://launchpadlibrarian.net/9512792/kern.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This shows the video detection process
** Attachment added: casper.log
http://launchpadlibrarian.net/9512805/casper.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: Original non-display xorg.conf
http://launchpadlibrarian.net/9512868/xorg.conf.20070926084629
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Doing a further
$sudo dpkg-reconfigure xserver-xorg
And choosing the Advanced monitor configuration option I set:
Horizontal Frequencies: 28-64
Vertical Frequencies: 43-60
Resolutions: 1024x768
Colour Depth: 24
When started, GDM correctly uses the entire LCD panel and
1024x768x24bpp.
** Attachment added: Working session Xorg.0.log
http://launchpadlibrarian.net/9512873/Xorg.0.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: ubiquity
Gutsy 32-bit LiveCD Beta (20070925.2) Install.
Choosing manual partitioning and assigning /boot /home and swap to pre-
existing (Feisty-created) partitions, the installer refuses to proceed
unless /boot is formatted.
This is clearly
Yes, it was misleading (if you don't read and *think* about it carefully!) but
ultimately it installed the correct 32-bit updates.
Maybe I was confused by it more because I'm heavily into 64- and 32-bit
development work and always having to double-check which target I'm building
for.
--
Finally got to test Gutsy 32-bit Beta (20070925.2) on Sony Vaio SRX51P
since the unionfs bug is (almost) sorted - the PC started albeit a few
problems still reported for unionfs.
However, the Lucent WaveLan/IEEE version 01.01 mini-pci card that is
interfaced via the pccard interface and works
Public bug reported:
Binary package hint: casper-udeb
Gutsy Desktop CD i386 32-bit Beta (20070925.2).
Loading on Sony Vaio SRX51P initial keyboard layout (consoles and xorg)
is US, not GB (UK), meaning and @, # and £ and maybe others are
transposed.
** Affects: casper (Ubuntu)
Well, the issue has recurred today. I had been using it without Cross-
fader. Before a PC restart I re-enabled Cross-fader in Rhythmbox.
After the restart Rhythmbox is back to using a large amount of CPU and
pushing the temperatures up. I tried disabling the plug-ins, one-
at-a-time, but with
Confirmed with Gutsy x86_64. Set desktop effects to None in gnome-
appearance-properties Visual Effects tab. Compiz stopped immediately.
Next time logging in realised Compiz is running, cube is active, *but*
gnome-appearance-properties Visual Effects tab shows None.
** Changed in: gdm (Ubuntu)
Public bug reported:
Binary package hint: compiz
Gutsy x86_64.
Whilst Compiz is enabled if a gnome-terminal window is drag-resized the
legend displaying the size during dragging is displayed as blocks rather
than numbers.
When Compiz is disabled the resize legend appears correct.
** Affects:
** Attachment added: gnome-terminal resize legend showing blocks
http://launchpadlibrarian.net/9529204/gnome-terminal-resize.png
--
gnome-terminal resize legend displayed as blocks when Compiz is enabled
https://bugs.launchpad.net/bugs/145604
You received this bug notification because you
Sebastien, in my case definitely gnome-appearance-manager.
--
Compiz not disabled by gnome-appearance-properties
https://bugs.launchpad.net/bugs/137941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Seems more applicable to nm-applet since it is responsible for managing
the keys.
** Summary changed:
- [Gutsy] Unable to connect to WPA2 if the AP was previously using WPA
+ [Gutsy] Unable to connect to Access Point if encryption method (WEP/WAP/WAP2)
of the AP is changed
** Also affects:
** Bug watch added: GNOME Bug Tracker #481181
http://bugzilla.gnome.org/show_bug.cgi?id=481181
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=481181
Importance: Unknown
Status: Unknown
--
CPU 60% and High Temperatures with Cross-Fader and low bit-rate
** Summary changed:
- CPU 60% and High Temperatures playing large MP3s
+ CPU 60% and High Temperatures with Cross-Fader and low bit-rate MP3
--
CPU 60% and High Temperatures with Cross-Fader and low bit-rate MP3
https://bugs.launchpad.net/bugs/141390
You received this bug notification because
Public bug reported:
Binary package hint: linux-source-2.6.22
Gutsy x86_64 with kernel 2.6.22-12-generic.
Up until a recent kernel update hibernate (and suspend) was working
fine. However, since the update hibernate seems to freeze the PC (in
/etc/acpi/hibernate.sh) at the point where it does:
This is the kern.log of a successful hibernate. GDM was stopped whilst
at the greeter stage after a cold boot.
** Attachment added: Successful hibernate kern.log
http://launchpadlibrarian.net/9529407/kern.log
--
Hibernate freezes PC before writing disk image
This is the output of /etc/acpi/hibernate.sh captured for the successful
hibernate action in the previous comment. It was captured by adding set
-x to the top of /etc/acpi/hibernate.sh and doing:
$ sudo su
$ /etc/acpi/hibernate.sh force 21 | tee /var/log/hibernate.log
** Attachment added:
This is the kern.log of an unsuccessful hibernate, captured using an
ACPI_DEBUG/PM_DEBUG kernel build.
** Attachment added: Unsuccessful hibernate DEBUG kern.log
http://launchpadlibrarian.net/9529424/kern-debug.log
--
Hibernate freezes PC before writing disk image
This is the output of /etc/acpi/hibernate.sh captured for the
unsuccessful hibernate action in the previous comment, using an
ACPI_DEBUG/PM_DEBUG kernel. It was captured by adding set -x to the
top of /etc/acpi/hibernate.sh and doing:
$ sudo su
$ /etc/acpi/hibernate.sh force 21 | tee
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
Hibernate freezes PC before writing disk image
https://bugs.launchpad.net/bugs/146196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
This is the kern.log of a successful hibernate with the
ACPI_DEBUG/PM_DEBUG kernel.
The PC was started from cold, and GDM stopped before log-in. the
hibernate was then activated manually:
$ sudo su
$ /etc/acpi/hibernate.sh force 21 | tee /var/log/hibernate.log
** Attachment added: Successful
This is the output of /etc/acpi/hibernate.sh captured for the successful
hibernate action in the previous comment, using an ACPI_DEBUG/PM_DEBUG
kernel. It was captured by adding set -x to the top of
/etc/acpi/hibernate.sh and doing:
$ sudo su
$ /etc/acpi/hibernate.sh force 21 | tee
*** This bug is a duplicate of bug 73744 ***
https://bugs.launchpad.net/bugs/73744
** Changed in: rhythmbox
Bugwatch: GNOME Bug Tracker #481181 = GNOME Bug Tracker #385061
** This bug has been marked a duplicate of bug 73744
rhythmbox is slow!
--
CPU 60% and High Temperatures with
In the latest Gutsy kernel images (looking at 2.6.22-13 here) vesafb is
no longer compiled into the kernel image as it was when this bug was
first reported. This is the reason the previous work-around no longer
works.
As MOM has reported, it is now necessary to remove the vesafb module
blacklist,
Confirmed here with LiveCD daily build of Gutsy 32-bit 20070912.1 on
Sony Vaio PCG-SRX51P.
[ 429.896000] BUG: unable to handle kernel NULL pointer dereference at virtual
address 00a0
[ 429.896000] printing eip:
[ 429.896000] c017ebbe
[ 429.896000] *pde =
[ 429.896000] Oops:
Adding linux-source-2.6.22 to this bug to bring attention to it
affecting Gutsy.
Running Gutsy 64-bit Tribe-5 + constant updates the root partition has
just run out of space:
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 5977156 5700308
I've been waiting to test it on the same hardware but so far Gutsy won't
install. Latest unionfs BUG issue is scheduled to be fixed for Gutsy
Beta... so let's hope :)
--
Crash - playing from iPod and view Source Properties
https://bugs.launchpad.net/bugs/73145
You received this bug notification
Public bug reported:
Binary package hint: network-manager
Gutsy 64-bit Tribe-5 + updates to 16th September, 2007.
NetworkManager: 0x2b3af925bc7f in waitpid () from
/lib/libpthread.so.0
On startup NetworkManager consistently fails, leaving
NetworkManagerDispatcher running. Once logged into
Public bug reported:
Binary package hint: network-manager-gnome
Gutsy Tribe-5 64-bit + updates to 16th September, 2007.
nm-applet no longer displays the animated 'connecting' icons ( the two
dots that change to green when WAP connects, and again on DHCP lease).
Instead, When reconnecting it
** Description changed:
Binary package hint: network-manager
- Gutsy 64-bit Tribe-5 + updates to 16th September, 2007.
+ Gutsy 64-bit Tribe-5 + updates to 16th September, 2007. Recent updates
+ (from /root/.synaptic/log/)
+
+ 2007-09-07.014923.log:26:network-manager (0.6.5-0ubuntu9) to
On a hunch I uninstalled VMware-server-1.0.3-44356 because I noticed it
was reporting a bridge attached to eth1, which is the WiFi interface.
After the first restart NetworkManager doesn't show this failure. I'll
continue to check on this after each restart and update the bug status
as
+1 on this.
It could do with some more documentation and localisation.
If the device has already been paired gbtsco won't discover it. The bond
needs to be deleted and the device rediscovered by btsco.
There also needs to be guidance on how to enable playback for the
Ubuntu-default players such
VMWare appears not to be the cause.
Starting the PC this morning from cold NetworkManager has consistently
failed to connect to WiFi - in fact I have had to connect a wired
connection to get any network connectivity. The workaround described
above of restarting NetworkManager(Dispatcher) hasn't
Public bug reported:
Binary package hint: network-manager
Gutsy 64-bit Tribe-5 + updates to 17th September 2007.
network-manager Version: 0.6.5-0ubuntu11
I've been happily running two Linksys Wifi access points (WRT54GL
WAP54G) with WPA-PSK using the stock Linksys firmware. Because the
WAP54G
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
The problem is gtk2 updates change the default font-rendering size to 50
To correct it, use this command by doing Alt+F2 (or a terminal if you
can see to type) and
$ gconftool --type float --set
The problem is gtk2 updates change the default font-rendering size to 50
To correct it, use this command by doing Alt+F2 (or a terminal if you
can see to type) and
$ gconftool --type float --set /desktop/gnome/font_rendering/dpi 96
** Changed in: gtk2-engines (Ubuntu)
Sourcepackagename:
** Summary changed:
- Gnome terminal doesn't show fonts
+ [Gutsy update] Gnome application font sizes too small to read
--
[Gutsy update] Gnome application font sizes too small to read
https://bugs.launchpad.net/bugs/140540
You received this bug notification because you are a member of Ubuntu
The problem appears to be in one of:
capplets-data_1%3a2.19.92-0ubuntu3
gnome-control-center_1%3a2.19.92-0ubuntu3
libgnome2-common_2.20.0-1ubuntu1
based on a script I ran that extracted the cached updates and searched
for anything affecting font_rendering setting:
Please check bug #140540 in case it is the cause of your issue.
--
cannot open terminal window
https://bugs.launchpad.net/bugs/140584
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
** This bug has been marked a duplicate of bug 140540
[Gutsy update] Gnome application font sizes too small to read
--
[gutsy] GNOME terminal has inhumanly small font (estimated point size about 0.2)
This is likely a side-effect of bug #140540 for which there is a fix.
--
themes manager is crashed (gutsy-gnome)
https://bugs.launchpad.net/bugs/140559
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
** This bug has been marked a duplicate of bug 140540
[Gutsy update] Gnome application font sizes too small to read
--
Gusty Tribe 5, open office wont start after update
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
** This bug has been marked a duplicate of bug 140540
[Gutsy update] Gnome application font sizes too small to read
--
gnome-appearence-properties fail to run since last update
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
** This bug has been marked a duplicate of bug 140540
[Gutsy update] Gnome application font sizes too small to read
--
cannot see text in terminal
https://bugs.launchpad.net/bugs/140593
You received this
In the Fiesty source-code tree you'll find them:
debian/config/amd64/config:2716:CONFIG_X86_POWERNOW_K8=m
debian/config/amd64/config:2717:CONFIG_X86_POWERNOW_K8_ACPI=y
debian/config/i386/config:2996:CONFIG_X86_POWERNOW_K8=m
debian/config/i386/config:2997:CONFIG_X86_POWERNOW_K8_ACPI=y
--
can not
:/sbin:/bin:/usr/bin/X11:/usr/games
- [EMAIL PROTECTED]
- SHELL=/bin/bash
- SourcePackage: gnome-terminal
- Uname: Linux Lifebook-hhs 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT
2007 i686 GNU/Linux
+ TJ: To correct it, use this command by doing Alt+F2 (or a terminal if
+ you can see to type
Could this be a side-affect of bug #140540 ?
--
No amarok gui, just empty window
https://bugs.launchpad.net/bugs/140578
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for amarok in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
** This bug has been marked a duplicate of bug 140540
[Gutsy update] Gnome application font sizes too small to read
--
blank gnome-terminal display except for blinking pixel
Confirmed with Gutsy 64-bit Tribe-5 with updates to 18th September,
2007.
The mouse sensitivity control doesn't affect the bluetooth mouse either.
Also, Gsynaptics sensitivity control doesn't affect the touchpad so this
might be a more general problem.
** Summary changed:
-
This is a regression; both work on the Feisty 32-bit installation on the
same PC.
** Changed in: gsynaptics (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: New = Confirmed
--
[gnome-mouse-properties] Sensitivity doesn't affect touchpad
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
** This bug has been marked a duplicate of bug 140540
[Gutsy update] Gnome application font sizes too small to read
--
Upgrade breaks terminal
https://bugs.launchpad.net/bugs/140603
You received this bug
*** This bug is a duplicate of bug 140591 ***
https://bugs.launchpad.net/bugs/140591
** This bug has been marked a duplicate of bug 140591
Openoffice won't launch
--
Openoffice.org will not start
https://bugs.launchpad.net/bugs/140605
You received this bug notification because you are a
From a terminal please try:
$ ooffice -writer %U
and report any warnings or errors that are displayed.
--
Openoffice won't launch
https://bugs.launchpad.net/bugs/140591
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The option works correctly here with a Synaptics glidepad on Sony Vaio,
with Gutsy 64-bit Tribe-5 + updates to 18th September 2007 and gnome-
control-center 1:2.19.92-0ubuntu3.
--
Tap to click option in Touchpad settings has no effect
https://bugs.launchpad.net/bugs/140599
You received this bug
** Changed in: gnome-app-install (Ubuntu)
Sourcepackagename: firefox = gnome-app-install
--
add/remove program fails
https://bugs.launchpad.net/bugs/140586
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Sebastien, I'm not sure but I think the libgnome changes may be the
reason for a massive surge of reports about fonts becoming too small to
read and gnome-appearances-properties crashing, summed up by bug #140540
and all its duplicates. I found the problem and a fix and posted the
details there,
301 - 400 of 2963 matches
Mail list logo
