Here is a patch. The only thing to change is that after applying the
patch against revision 2216 of the tree, you need to change line 179 to
correctly iterate of the GList of children. I am not a gtk+ expert, I am
using it only through pygtk.
This obviously needs testing as I was not able to do
Thank you! My wife told me last week, hey I do not want to write on my
original CD! Are you sure it will work ok? So please bump it!
--
Label is write instead of copy
https://bugs.launchpad.net/bugs/47889
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Using Hardy I have no problems at the moment. If I can remember
correctly the latest updates of Gutsy solved the problem too as I can't
remember the last time when I had to go through these kill/start
sequences.
--
dhclient already running, must kill to connect with wireless
The sound is working perfectly well with the Hardy Heron 8.04 release. I
think this bug can be marked as fixed.
--
Gutsy: Sound not working on X61s with Intel AD1984
https://bugs.launchpad.net/bugs/130923
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I confirm, this is working with Hardy Heron.
--
cannot change brightness in Gutsy with thinkpad X61s
https://bugs.launchpad.net/bugs/129913
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: evolution
When the connection is reset by peer, we get a modal dialog box error.
This is annoying because evolution is anyway doing the reconnection
right after with the need for the user to do anything. Basically this
dialog box is just interrupting the
** Attachment added: The very annoying dialog box
http://launchpadlibrarian.net/9529449/Screenshot-Evolution%20Error.png
--
Connection reset by peer warning should be in the status bar
https://bugs.launchpad.net/bugs/146199
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: file-roller
File roller crashed at the end of the creation of a zip archive. The zip
file was correctly created and renamed from the temporary name to the
requested file name. The size of the final archive was about 10MB with 8
pictures in it. This
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/9520441/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/9520442/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/9520443/Disassembly.txt
** Attachment
This bug could be related to the bug #122973 but I am not sure.
** Visibility changed to: Public
--
[Gutsy] file-roller crashed with SIGSEGV
https://bugs.launchpad.net/bugs/145487
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
After restarting my system (X61s) this morning, it is now working. I
have a pack of 42 updates to install now, I will install them and do
some further testing.
--
wifi needs to be switched off then back on again in order for network-manager
to use it.
https://bugs.launchpad.net/bugs/119563
You
Yeah! It now works for me! Even after a suspend!
--
wifi needs to be switched off then back on again in order for network-manager
to use it.
https://bugs.launchpad.net/bugs/119563
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
For me it looks like the fix fixed it, I will reopen a bug in case of
troubles. Thanks! (ThinkPad X61s)
--
kernel oops after resuming from suspend to RAM
https://bugs.launchpad.net/bugs/129226
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Is the fix already released? Because I have a fully up-to-date Gutsy and
I got an oops just 10 minutes ago when going out of suspend.
--
kernel oops after resuming from suspend to RAM
https://bugs.launchpad.net/bugs/129226
You received this bug notification because you are a member of Ubuntu
** Attachment added: Output of printingbuginfo
http://launchpadlibrarian.net/8877034/printingbuginfo
--
Gutsy: Printing not working with HP 1320n (after upgrade the 16/8)
https://bugs.launchpad.net/bugs/132900
You received this bug notification because you are a member of Ubuntu
Bugs, which
The job 34 is the one I started in debug mode.
If you need more info, please let me know.
** Attachment added: Cups error log
http://launchpadlibrarian.net/8877064/error_log
--
Gutsy: Printing not working with HP 1320n (after upgrade the 16/8)
https://bugs.launchpad.net/bugs/132900
You
Public bug reported:
Binary package hint: cupsys
Since last upgrade (the 16th of August) I can't print any more on my HP
1320n. I don't know if this related to the removal of gnome-cups-manager
package during the upgrade procedure.
System: Gutsy with latest upgrades
If you need more info, like
[EMAIL PROTECTED]:~$ uname -a
Linux carbon 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
The system is ThinkPad X61s and I have added the following boot
parameter: acpi_sleep=s3_bios
Else it is installed fresh from a Tribe 3 and then upgraded.
--
Gutsy: Kernel panic after
** Attachment added: lspci -vvnn for X61s output
http://launchpadlibrarian.net/8766834/lspci-vvnn-kernelpanic.log
--
Gutsy: Kernel panic after resuming from suspend to ram
https://bugs.launchpad.net/bugs/131468
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: linux-source-2.6.22
I have a kernel when going out of suspend to ram.
It can be related to the following bugs, but I am no really sure:
bug #129226 and bug #60323
Find attached the different debug outputs.
** Affects: linux-source-2.6.22 (Ubuntu)
** Attachment added: dmesg output
http://launchpadlibrarian.net/8766832/dmesg-kernelpanick.log
--
Gutsy: Kernel panic after resuming from suspend to ram
https://bugs.launchpad.net/bugs/131468
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: dmesg output
http://launchpadlibrarian.net/8742494/dmesg.log
--
wifi needs to be switched off then back on again in order for network-manager
to use it.
https://bugs.launchpad.net/bugs/119563
You received this bug notification because you are a member of Ubuntu
Bugs,
As this morning I got an update of the network manager, here is a new
dmesg and daemon.log
** Attachment added: daemon.log with the kill sequence
http://launchpadlibrarian.net/8742490/daemon.log
--
wifi needs to be switched off then back on again in order for network-manager
to use it.
** Attachment added: lspci -vvnn for X61s output
http://launchpadlibrarian.net/8736296/lspci-vvnn.log
--
wifi needs to be switched off then back on again in order for network-manager
to use it.
https://bugs.launchpad.net/bugs/119563
You received this bug notification because you are a
Ok, it looks like have the same problem with a X61s. Here are attached
the info you requested:
$ uname- a
Linux carbon 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
** Attachment added: dmesg output
http://launchpadlibrarian.net/8736286/dmesg.log
--
wifi needs to be
I must add that this is the procedure I am using to be able to get a
wifi connection:
- Enable wifi in the network manager applet
- Select the network I want to connect
- Switch on the kill switch
- Switch off the kill switch to get again the wifi.
- Then it works
So I always need this switching
Ok here is what I did and you have the daemon.log attached.
At about 20:25 I put the computer out of sleep.
At 20:25 I had to activate the kill switch and then I activated the wifi again
at 20:26.
At 20:27 I was connected on the HELIUM network.
You know most likely better than me how to read
Public bug reported:
Binary package hint: notification-daemon
See the attached screenshot. This is in Gutsy.
** Affects: notification-daemon (Ubuntu)
Importance: Undecided
Status: New
--
Gutsy. The background color of the notification area is not the good one
** Attachment added: Show the dark gray color
http://launchpadlibrarian.net/8721076/bad-color-notification.png
--
Gutsy. The background color of the notification area is not the good one
https://bugs.launchpad.net/bugs/130858
You received this bug notification because you are a member of
I have a X61s, the problem with the brightness comes from the fact that
the X61s has 16 levels of brightness and this is not well supported for
the moment by the ACPI code.
See: http://www.mail-archive.com/ibm-acpi-
[EMAIL PROTECTED]/msg00692.html
--
cannot change brightness in Gutsy
Public bug reported:
Sound is not working on the X61s as the needed alsa drivers is not yet
available.
Taken from here: http://www.linux-on-laptops.com/hosted/lenovo-ibm-
x61s.html
Sound, as mentioned, does not work out of the box. It is actually to
blame on the AD1984 codec chip that is not
Public bug reported:
Binary package hint: compiz
My hardware configuration is a laptop (X61s) with an external screen
connected through a docking station. The laptop screen is closed in that
case.
Laptop screen resolution 1024x768
External screen: 1280x1024
When doing a full screen of a window
Installing Feisty with upgraded bios on my T41p, the problem is still there (no
temperature polling), but this time I have a clean way to solve the problem.
I have added a script to set the polling and the trip points at start and
resume:
/etc/acpi/resume.d/99-set-acpi-polling-trip-points.sh
I have the same problem:
Laptop: IBM T41p
Ubuntu: Dapper works perfectly/Edgy gives Critical Temperature Reached messages
in kern.log and halt with T ~= 94 C
Upgrade procedure from Dapper: /home kept, format and install of /
Good point: acpi kicks in and protect my hardware!
Bad point: CPU freq
Ok, I took a look at my DSDT and tried to recompile it with iasl and got
some errors. So I will explore the DSDT case further. If you want to
recompile your DSDT:
To get the compiler: https://help.ubuntu.com/community/ACPIBattery
To get your current DSDT and fix it:
Interesting: Upgrading my bios and microcontroller version to the latest from
2.11 to 3.21 and now when I check my DSDT file and recompile it I have no
errors.
http://www.thinkwiki.org/wiki/BIOS_Upgrade
More interesting for not T41p owners with such problems. As you can see
in my previous
Interesting, running the same script with dapper (not tested on breezy)
with a Canon LiDE 25 is causing a segmentation fault too at the same
stage, but my error in /var/log/messages is:
Sep 18 19:07:08 localhost python: hpssd [WARN] Inrecognized URI:
socket://printer2l:9100
Sep 18 19:07:08
Merci !
--
Label is write instead of copy
https://launchpad.net/bugs/47889
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
38 matches
Mail list logo
