[Bug 261441] Re: Suspend mode don't work on Fujitsu Siemens Amilo Li 2732
I'm sorry to break the good mood here, but I still get problems suspending on my Fujitsu Siemens Amilo Li 2735. Trying both 8.10 i386 and 9.10 alpha4 desktop live cd's the issue appears fixed, but: * after a few correct suspend requests running live cd at a point the system is unable to correctly recover (keyboard is no longer working, screen not updating) * immediately after installing from the LiveCD I can solidly reproduce the problem (blank screen after suspend, from console or X11) --- actually the sequence is a bit longer: when trying to resume there is a brief "powerup" sequence then immediately drops power then one second later there is yet another powerup but remains in blank screen Let me know what other debugging information you need. ** Changed in: linux (Ubuntu) Status: Fix Released => New -- Suspend mode don't work on Fujitsu Siemens Amilo Li 2732 https://bugs.launchpad.net/bugs/261441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337470] Re: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure
Tried running pm-suspend from the console two times (with Xorg running and also stopped) and I still get the same double power-up and hang sequence upon trying to resume. No messages since the console remained blank. Should I try to mess up again with the DebuggingKernelSuspend method ? -- [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure https://bugs.launchpad.net/bugs/337470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261441] Re: Suspend mode don't work on Fujitsu Siemens Amilo Li 2732
Further testing on my Amilo Li 2735: * suspend/resume while booted with the Jaunty i386 alpha4 LiveCD is just fine, any attempt to suspend from the HDD install from the very same CD fails every time (with the same resume/powerup/powerdown/powerup/hang behavior) * I do not see a second powerup sequence when resuming from LiveCD (goes resume/powerup/working), but I do see some SquashFS errors after resuming * checking for loaded modules in the LiveCD and HDD install reveals no new modules loaded in the HDD install (less even) * checking for dmesg differences reveals no significant differences (only some memory sizes/offsets different, some modules loaded in a different order), except perhaps a TSC statement -- see attachment. I have tried the pm_trace method described in https://wiki.ubuntu.com/DebuggingKernelSuspend to no avail (no code is pinpointed). What else can I do to debug this issue ? ** Attachment added: "Differences between LiveCD dmesg and HDD-install dmesg" http://launchpadlibrarian.net/23388012/fj-2735-dmesg.diff -- Suspend mode don't work on Fujitsu Siemens Amilo Li 2732 https://bugs.launchpad.net/bugs/261441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337470] [NEW] [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure
Public bug reported: Spin-off from #261441: * suspend/resume while booted with the Jaunty i386 alpha4 LiveCD is just fine, any attempt to suspend from the HDD install from the very same CD fails every time -- when trying to resume there is a brief "powerup" sequence then immediately drops power then one second later there is yet another powerup but hangs in a blank screen * I do not see a second powerup sequence when resuming from LiveCD (goes resume/powerup/working), but I do see some SquashFS errors after resuming * checking for loaded modules in the LiveCD and HDD install reveals no new modules loaded in the HDD install (less even) * checking for dmesg differences reveals no significant differences (only some memory sizes/offsets different, some modules loaded in a different order), except perhaps a TSC statement -- see attachment. I have tried the pm_trace method described in https://wiki.ubuntu.com/DebuggingKernelSuspend to no avail (no code is pinpointed). In the mean time I have upgraded to current Jaunty but I still get the same behavior from GUI suspend. Details: Linux fujilaptop 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686 GNU/Linux ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: FUJITSU SIEMENS AMILO Li 2735 Package: linux-image-2.6.28-8-generic 2.6.28-8.26 ProcAttrCurrent: unconfined ProcCmdLine: User Name=UUID=e77fdfc4-fec6-4daa-915a-1dfa426c82de ro ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-8.26-generic SourcePackage: linux StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log' Tags: resume suspend Title: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure UserGroups: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure https://bugs.launchpad.net/bugs/337470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337470] Re: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure
** Attachment added: "dmesg output" http://launchpadlibrarian.net/23394288/dmesg.log ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/23394289/BootDmesg.txt ** Attachment added: "CurrentDmesg.gz" http://launchpadlibrarian.net/23394290/CurrentDmesg.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/23394291/Dependencies.txt ** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/23394292/HalComputerInfo.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/23394293/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/23394294/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/23394295/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/23394296/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/23394297/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/23394298/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/23394299/ProcStatus.txt -- [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure https://bugs.launchpad.net/bugs/337470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261441] Re: Suspend mode don't work on Fujitsu Siemens Amilo Li 2732
I have opened a separate bug #337470 since Apparmor caught a kernel OOPS upon resume. If you consider that the symptoms on Amilo Li 2732 are different / is fixed versus Li 2735 then please go ahead closing this bug since I will be continuing in #337470. -- Suspend mode don't work on Fujitsu Siemens Amilo Li 2732 https://bugs.launchpad.net/bugs/261441 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337470] Re: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure
Just updated the machine to the latest Jaunty and the symptoms are worse now -- the machine does one powerup then powersoff and remains powered off. Please note that a similar issue is present when normally powering off the machine from the system menu: after the shutdown is complete and machine has automatically powered off, when I press the power button the machine powers up for a short amount of time then powers off and I have to press the power button a second time to have it booting (normally). My guess is that there is a double-suspend/poweroff quirck enabled by default which does not play well with the Fujitsu Siemens hardware. -- [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure https://bugs.launchpad.net/bugs/337470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154393] Re: [Firefox] security update release 2.0.0.8 available from upstream
Seen update to 2.0.0.8 in today's updates. Thank you. -- [Firefox] security update release 2.0.0.8 available from upstream https://bugs.launchpad.net/bugs/154393 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154393] Re: [Firefox] security update release 2.0.0.8 available from upstream
Strangely, although the bug is marked as fixed (also) for Gutsy, up-to- date installation still have 2.0.0.6: $ apt-cache show firefox Package: firefox Priority: optional Section: web Installed-Size: 26008 Maintainer: Alexander Sack <[EMAIL PROTECTED]> Architecture: i386 Version: 2.0.0.6+2nobinonly-0ubuntu1 Also checked the apt archive and there is no 2.0.0.8 version present in main or universe repositories. Could you please clarify ? -- [Firefox] security update release 2.0.0.8 available from upstream https://bugs.launchpad.net/bugs/154393 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155306] [gutsy] black boxes for fixed font windows resize
Public bug reported: Binary package hint: compiz Up-to-date Ubuntu Gutsy. When resizing a fixed-font window (e.g. a terminal window) I can only see black filled boxes for the window size string. A similar issue can be seen with the Window Switcher, only the letter boxes are filled with a lighter shade of gray and one can distinguish the black letters inside. Over the time this issue has come and go on successive updates. I have tried to fix this issue from Advanced Desktop Effects Settings, but found no controls for it. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- [gutsy] black boxes for fixed font windows resize https://bugs.launchpad.net/bugs/155306 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131554] Re: [gutsy] CTRL+ALT+C shortcut for glipper does not work
I found this feature works in latest Ubuntu Gutsy (updated) ** Changed in: glipper (Ubuntu) Status: New => Invalid -- [gutsy] CTRL+ALT+C shortcut for glipper does not work https://bugs.launchpad.net/bugs/131554 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] Re: [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
No, running Pidgin under valgrind does not crash. I use this as a workaround to be able to use Pidgin (albeit quite slow) :). -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132888] [gutsy] firefox randomly hangs when opening new windows / popups
Public bug reported: Binary package hint: firefox Under Ubuntu Gutsy, updated daily, ever since the libc6/glibc update about a week ago, the Firefox browser would hang with 100% CPU usage every now and then, when opening a new window with CTRL+N or a popup is to be shown. I will try to get a stacktrace at the time of the hang with gdb and firefox-dbg symbols. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: firefox gutsy hang ** Description changed: Binary package hint: firefox Under Ubuntu Gutsy, updated daily, ever since the libc6/glibc update about a week ago, the Firefox browser would hang with 100% CPU usage every now and then, when opening a new window with CTRL+N or a popup is to be shown. - I will try to get a stackgrace at the time of the hang with gdb and + I will try to get a stacktrace at the time of the hang with gdb and firefox-dbg symbols. ** Tags added: firefox gutsy hang -- [gutsy] firefox randomly hangs when opening new windows / popups https://bugs.launchpad.net/bugs/132888 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132888] Re: [gutsy] firefox randomly hangs when opening new windows / popups
** Attachment added: "GDB stacktrace, 3.2Mb uncompressed" http://launchpadlibrarian.net/8849258/gdb-firefox-libc6.txt.gz -- [gutsy] firefox randomly hangs when opening new windows / popups https://bugs.launchpad.net/bugs/132888 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132888] Re: [gutsy] firefox randomly hangs when opening new windows / popups
>From the GDB stacktrace it looks like the culprit is a deep recursion
issue in Google Toolbar's JS code:
#75 0xb7070635 in nsXPCException::NewException (aMessage=0xd2bc5b8
"'[JavaScript Error: \"too much recursion\" {file:
\"file:///home/ady/.mozilla/firefox/u5dac8ym.default/extensions/%7B3112ca9c-de6d-4884-a869-9855de68056c%7D/lib/toolbar.js\"
line: 40}]' when calling metho"..., aResult=2153185313, aLocation=0x0,
aData=0xd344050, exceptn=0xbfe6e22c) at xpcexception.cpp:442
xpc = (class nsXPConnect *) 0x63rv =
e = (nsXPCException *) 0xcd21260
#76 0xb706bc86 in XPCConvert::ConstructException (rv=2153185313,
message=0xd0d4c28 "[JavaScript Error: \"too much recursion\" {file:
\"file:///home/ady/.mozilla/firefox/u5dac8ym.default/extensions/%7B3112ca9c-de6d-4884-a869-9855de68056c%7D/lib/toolbar.js\"
line: 40}]", ifaceName=0xafe73468 "nsIObserver", methodName=0x8154d40
"observe", data=0xd344050, exceptn=0xbfe6e22c) at xpcconvert.cpp:1287
msg = 0xd0d4c28 "[JavaScript Error: \"too much recursion\" {file:
\"file:///home/ady/.mozilla/firefox/u5dac8ym.default/extensions/%7B3112ca9c-de6d-4884-a869-9855de68056c%7D/lib/toolbar.js\"
line: 40}]"
sz = 0xd2bc5b8 "'[JavaScript Error: \"too much recursion\" {file:
\"file:///home/ady/.mozilla/firefox/u5dac8ym.default/extensions/%7B3112ca9c-de6d-4884-a869-9855de68056c%7D/lib/toolbar.js\"
line: 40}]' when calling metho"...
res =
format = "'%s' when calling method: [%s::%s]"
I have disabled the Google Toolbar extension and all looks well now.
--
[gutsy] firefox randomly hangs when opening new windows / popups
https://bugs.launchpad.net/bugs/132888
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132901] [gutsy] Cannot set / remeber from Nautilus the default application with which to open archived files in file-roller
Public bug reported: Binary package hint: file-roller File roller version 2.19.90-0ubuntu1 in Ubuntu Gutsy 7.10 up-to-date. While in Ubuntu Feisty the File roller utility you would get to choose what application you will use to open certain files and remember that choice, in Ubuntu Gutsy the file-roller will always open by default the gEdit editor even though I want gVim (and have set that option in Nautilus), which forces me to always use "Open with". I understood from other file-roller bugs that a new behavior has been implemented -- to detect file type after extraction and open based on mime-types. It would be nice if file-roller would respect the same user choices when opening files as Nautilus does. Perhaps adding xdg-open support would help. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- [gutsy] Cannot set / remeber from Nautilus the default application with which to open archived files in file-roller https://bugs.launchpad.net/bugs/132901 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132888] Re: [gutsy] firefox randomly hangs when opening new windows / popups
Confirmed, this was a Google Toolbar issue -- not reproducible since disabling the extension. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- [gutsy] firefox randomly hangs when opening new windows / popups https://bugs.launchpad.net/bugs/132888 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131050] Re: [gutsy] Clock applet calendar/timezones opens under focused window
Quick workaround: click on the currently focused window -- it will make the applet window correctly resurface above the focused window. -- [gutsy] Clock applet calendar/timezones opens under focused window https://bugs.launchpad.net/bugs/131050 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] Re: [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
Found the root cause: I was sharing the .purple configuration directory between two Ubuntu installations (symlink between homes), Feisty and Gutsy. When I recreated the Pidgin configuration from scratch in Gutsy, the crashes stopped reproducing. In more detail, I found that the accounts.xml file from the Feisty installation (also Pidgin 2.1.0) would trigger the crash. -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
Public bug reported: Binary package hint: pidgin Immediately after updating libc6 today (and restarting the system), Pidgin would keep crashing upon starting it up (automatic accounts logging in, automatic joining to a few XMPPS chat rooms). Pidgin was working just fine previous to today's libc6 update. ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: libc6 pidgin ** Description changed: Binary package hint: pidgin - Immediately after updating lic6 today (and restarting the system), + Immediately after updating libc6 today (and restarting the system), Pidgin would keep crashing upon starting it up (automatic accounts logging in, automatic joining to a few XMPPS chat rooms). Pidgin was working just fine previous to today's libc6 update. -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] Re: [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
Here is attached the gdb crash backtrace. Surprisingly, under valgrind it did not crash... More details: $ apt-cache show libc6 Package: libc6 Priority: required Section: base Installed-Size: 10108 Maintainer: Ubuntu Core developers <[EMAIL PROTECTED]> Original-Maintainer: GNU Libc Maintainers <[EMAIL PROTECTED]> Architecture: i386 Source: glibc Version: 2.6.1-0ubuntu1 Provides: glibc-2.6-1 Depends: libgcc1 Suggests: locales, glibc-doc Conflicts: libterm-readline-gnu-perl (<< 1.15-2), tzdata (<< 2007e-2) Filename: pool/main/g/glibc/libc6_2.6.1-0ubuntu1_i386.deb Size: 4182062 MD5sum: c248f12b4a75bf618881082f740b023c SHA1: 78a4f7dacaa8f11ff0aa25a162ffa371d9db1710 SHA256: 5b05accee952294549f7c51fd1f87cba8823602fde815752f13b8825bf5d41dd Description: GNU C Library: Shared libraries Contains the standard libraries that are used by nearly all programs on the system. This package includes shared versions of the standard C library and the standard math library, as well as many others. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu ** Attachment added: "GDB crash backtrace" http://launchpadlibrarian.net/8721824/gdb-pidgin.txt -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94130] Re: apport fails to use environment proxy configuration
Because of this bug I am unable to report any crashes in Gutsy. It would be very important to have this functionality enabled. -- apport fails to use environment proxy configuration https://bugs.launchpad.net/bugs/94130 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131050] [gutsy] Clock applet calendar/timezones opens under focused window
Public bug reported: Binary package hint: compiz-gnome Ubuntu Gutsy, up-to-date. Clicking on the Clock applet will show the calendar underneath the currently focused application window. If the current window is maximized then nothing will appear. $ apt-cache show compiz-gnome Package: compiz-gnome Priority: optional Section: x11 Installed-Size: 1384 Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]> Original-Maintainer: Debian X Strike Force <[EMAIL PROTECTED]> Architecture: i386 Source: compiz Version: 1:0.5.2-0ubuntu1 Replaces: compiz-gtk (<= 1:0.3.6-1ubuntu13) Depends: compiz-core (= 1:0.5.2-0ubuntu1), compiz-plugins (= 1:0.5.2-0ubuntu1), libart-2.0-2 (>= 2.3.18), libatk1.0-0 (>= 1.13.2), libbonobo2-0 (>= 2.15.0), libbonoboui2-0 (>= 2.15.1), libc6 (>= 2.6), libcairo2 (>= 1.4.0), libdbus-1-3 (>= 1.1.1), libdbus-glib-1-2 (>= 0.74), libdecoration0, libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.3.5), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.13.7), libgnome-desktop-2 (>= 2.11.1), libgnome-window-settings1, libgnome2-0 (>= 2.17.3), libgnomecanvas2-0 (>= 2.19.1), libgnomeui-0 (>= 2.19.1), libgnomevfs2-0 (>= 1:2.17.90), libgtk2.0-0 (>= 2.11.6), libice6 (>= 1:1.0.0), libmetacity0 (>= 1:2.19.5), liborbit2 (>= 1:2.14.8), libpango1.0-0 (>= 1.17.5), libpng12-0 (>= 1.2.13-4), libpopt0 (>= 1.10), libsm6, libstartup-notification0 (>= 0.8-1), libwnck22 (>= 2.19.5), libx11-6, libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 1:4.0.1), libxi6, libxinerama1, libxrandr2 (>= 2:1.2.0), libxrender1, zlib1g (>= 1:1.2.3.3.dfsg-1), gconf2 (>= 2.12.1-1), libcompizconfig-backend-gconf Suggests: gnome-themes Conflicts: compiz-gtk (<= 1:0.3.6-1ubuntu13) Filename: pool/main/c/compiz/compiz-gnome_0.5.2-0ubuntu1_i386.deb Size: 168176 MD5sum: 3fa97e02bbe693289f4fe7021fb3fbd5 SHA1: ebe75f897593a4d424ab70d3be5681e1c470 SHA256: 67d5fb152f053208cdd74fe29d971994b6e88baf876ce64487a979a6cc1a0ee8 $ apt-cache show compiz-core Package: compiz-core Priority: optional Section: x11 Installed-Size: 1576 Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]> Original-Maintainer: Debian X Strike Force <[EMAIL PROTECTED]> Architecture: i386 Source: compiz Version: 1:0.5.2-0ubuntu1 Depends: libc6 (>= 2.6), libgl1-mesa-glx | libgl1, libice6 (>= 1:1.0.0), libsm6, libstartup-notification0 (>= 0.8-1), libx11-6, libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 1:4.0.1), libxinerama1, libxml2 (>= 2.6.29), libxrandr2 (>= 2:1.2.0), libxslt1.1 (>= 1.1.20), mesa-utils Recommends: compiz-plugins (= 1:0.5.2-0ubuntu1) Suggests: nvidia-glx (>= 1.0.9625-1) Breaks: compiz-extra (<= 0.3.6.1-0ubuntu2), libcompizconfig0 (<< 0.0+git20070725) Filename: pool/main/c/compiz/compiz-core_0.5.2-0ubuntu1_i386.deb Size: 185954 MD5sum: 461e9641e1b68923adba35395b0c889f SHA1: 2bdf0bd7e507eaaf2f42c432dd9c84e744a954b3 SHA256: bf5b45ba36209651eaa884d60582fd3993bbf4d3eed47d526e925816f0d68879 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- [gutsy] Clock applet calendar/timezones opens under focused window https://bugs.launchpad.net/bugs/131050 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131554] [gutsy] CTRL+ALT+C shortcut for glipper does not work
Public bug reported: Binary package hint: glipper Tried to use Glipper's shortcut in Gutsy with various applications (Firefox, gEdit, Terminal), but the expected menu does not show up. Tried to change the shortcut key but still no luck. Same functionality is working in Feisty. ** Affects: glipper (Ubuntu) Importance: Undecided Status: New -- [gutsy] CTRL+ALT+C shortcut for glipper does not work https://bugs.launchpad.net/bugs/131554 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] Re: [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
My problem has been fixed with the latest updates. I have not seen any libc6 update, but something somehow fixed my problem. -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] Re: [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
Once again, after the latest round of updates, Pidgin crashes again, backtrace appears to indicate an issue in libc6's free() ? Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1224808240 (LWP 6439)] 0xb75ac7cc in free () from /lib/tls/i686/cmov/libc.so.6 ** Attachment added: "GDB crash backtrace [2]" http://launchpadlibrarian.net/8806984/gdb-pidgin-libc6.txt ** Also affects: libc (Ubuntu) Importance: Undecided Status: New -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130852] Re: [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
Right name for libc6 is glibc ** Changed in: glibc (Ubuntu) Sourcepackagename: libc => glibc -- [gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6 https://bugs.launchpad.net/bugs/130852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145604] Re: gnome-terminal resize legend displayed as blocks when Compiz is enabled
I am in the very same situation (gradual updates until final Gutsy release). I can think of two possible tests right now: 1. "flush" all compiz settings in order to revert to default setup (or even certain plugin(s) settings) 2. Switch to "i810" driver instead of "intel" driver 3. upgrade or reinstall with a fresh Gutsy release CD I would rather take option (1) from the two above. Particular things to my machine: Dell laptop with Intel 945GM card using "intel" driver, 1280x1024 on CRT output, 1440x960 on LCD (with 915resolution). Let me know what other infos may be relevant in this context. -- 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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145604] Re: gnome-terminal resize legend displayed as blocks when Compiz is enabled
I can confirm that creating a new user fixes the problem. I have "flushed" all GNOME configuration files in my home directory and the problem has disappeared. I guess fixing up some or most of the ~/.gconf/apps/compiz/ hierarchy would resolve the problem. I have not tried yet Preferences / Advanced Desktop Settings (need compizconfig) / Preferences / Reset to Defaults , although I remember to have used it once in the past. -- 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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131050] Re: [gutsy] Clock applet calendar/timezones opens under focused window
Confirming: the fix works. -- [gutsy] Clock applet calendar/timezones opens under focused window https://bugs.launchpad.net/bugs/131050 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162854] Re: [Gutsy] kernel runs out of memory: Out of memory / invoked oom-killer
Found out that the installation was corrupted (had all kinds of signal traps generated by the screensaver). After reinstalling from an original Ubuntu 64bit disc everything seems to work fine. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New => Invalid -- [Gutsy] kernel runs out of memory: Out of memory / invoked oom-killer https://bugs.launchpad.net/bugs/162854 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164467] [enh] Need to sense docking station / switch video output
Public bug reported: Binary package hint: hal-device-manager I have a laptop which I'm daily changing it from docked (in the morning) and undocked (evening). My usual procedure is to suspend (standby) the laptop before docking/undocking. When I do [docked]suspend+undock+resume or [undocked]suspend+dock+resume I don't get the video output switched automatically (and thus have no video displayed). I would need to press Fn+F7 or ScrollLock+F7 to trigger a video output switch (I am using intel xorg driver). However, my screen is automatically locked upon suspend so I first need to enter the password, but I cannot see the screen. Furthermore, on my Logitech keyboard hooked to the docking station I am unable to produce ScrollLock+F7 due to special function keys rearrangements. I would need an enhancement like this: * somehow have the HAL daemon be notified of dock/undock status (or even status change) * once HAL daemon detected a docking change then it should trigger a video output switch by calling the appropriate xorg driver hook (if possible specify which is the current active video output). ** Affects: hal (Ubuntu) Importance: Undecided Status: New -- [enh] Need to sense docking station / switch video output https://bugs.launchpad.net/bugs/164467 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154210] Re: Massive memory leak in compiz
*** This bug is a duplicate of bug 151168 *** https://bugs.launchpad.net/bugs/151168 I see the same problem with compiz.real process growing in size, but with an Intel video card: ady 5512 0.3 67.2 1554180 1380664 ? SDec03 4:11 /usr/bin/compiz.real --ignore-desktop-hints --replace --indirect- rendering --sm-client-id default0 ccp That comes around 1.3Gb of resident memory on a 2Gb RAM machine. Hardware is Dell OptiPlex GX620 with an Intel 82945G/GZ video chipset driven by the "intel" xorg driver, OS is Ubuntu Gusty 7.10 amd64 freshly installed. So this quite excludes the video driver as a root cause. Machine has been perfectly running previously with Ubuntu Gutsy 7.10 i386 (32bit). This leads me thinking there is an issue in Compiz when compiled as 64bit binary. Let me know what other data you would need me to upload. I think it's best that we unlink this bug from #151168 since that one is directly tied to the NVIDIA driver. -- Massive memory leak in compiz https://bugs.launchpad.net/bugs/154210 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162854] [Gutsy] kernel runs out of memory: Out of memory / invoked oom-killer
Public bug reported: Binary package hint: linux-image-2.6.22-14-generic Ever since installing Ubuntu Gutsy 7.10 amd64 on a Intel P4 machine, I see that the kernel is killing processes every night -- dmesg output is full of seqeuences like these: [55217.708860] printk: 66 messages suppressed. [55217.708869] cron invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0 [55217.708872] [55217.708873] Call Trace: [55217.708899] [] out_of_memory+0x2b6/0x330 [55217.708930] [] __alloc_pages+0x2f8/0x350 [55217.708970] [] __do_page_cache_readahead+0x107/0x2a0 [55217.708999] [] io_schedule+0x28/0x40 [55217.709029] [] mntput_no_expire+0x27/0xc0 [55217.709043] [] link_path_walk+0x80/0xf0 [55217.709072] [] filemap_nopage+0x238/0x2f0 [55217.709106] [] __handle_mm_fault+0x1c4/0xb60 [55217.709159] [] do_page_fault+0x1fc/0x870 [55217.709212] [] sys_newstat+0x36/0x50 [55217.709245] [] error_exit+0x0/0x84 [55217.709299] [55217.709301] Mem-info: [55217.709304] Node 0 DMA per-cpu: [55217.709308] CPU0: Hot: hi:0, btch: 1 usd: 0 Cold: hi:0, btch: 1 usd: 0 [55217.709313] CPU1: Hot: hi:0, btch: 1 usd: 0 Cold: hi:0, btch: 1 usd: 0 [55217.709316] Node 0 DMA32 per-cpu: [55217.709321] CPU0: Hot: hi: 186, btch: 31 usd: 46 Cold: hi: 62, btch: 15 usd: 26 [55217.709325] CPU1: Hot: hi: 186, btch: 31 usd: 32 Cold: hi: 62, btch: 15 usd: 49 [55217.709331] Active:226894 inactive:243957 dirty:0 writeback:0 unstable:0 [55217.709333] free:3482 slab:3968 mapped:22 pagetables:3324 bounce:0 [55217.709336] Node 0 DMA free:8000kB min:28kB low:32kB high:40kB active:2020kB inactive:1720kB present:11276kB pages_scanned:12151 all_unreclaimable? yes [55217.709344] lowmem_reserve[]: 0 1994 1994 [55217.709349] Node 0 DMA32 free:5928kB min:5700kB low:7124kB high:8548kB active:905556kB inactive:974108kB present:2042752kB pages_scanned:3598243 all_unreclaimable? yes [55217.709357] lowmem_reserve[]: 0 0 0 [55217.709362] Node 0 DMA: 0*4kB 0*8kB 0*16kB 2*32kB 0*64kB 0*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 1*4096kB = 8000kB [55217.709376] Node 0 DMA32: 58*4kB 28*8kB 2*16kB 0*32kB 1*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 1*4096kB = 5928kB [55217.709391] Swap cache: add 98564, delete 98564, find 13/18, race 0+0 [55217.709394] Free swap = 0kB [55217.709396] Total swap = 393552kB [55217.709398] Free swap:0kB [55217.735822] 521862 pages of RAM [55217.735826] 8350 reserved pages [55217.735828] 27266 pages shared [55217.735830] 0 pages swap cached [55217.741480] Out of memory: kill process 5103 (x-session-manag) score 146566 or a child [55217.741491] Killed process 5275 (vino-session) $ free total used free sharedbuffers cached Mem: 2054052 4054601648592 0 61908 108164 -/+ buffers/cache: 2353881818664 Swap: 393552 96408 297144 $ uname -a Linux apenisoara 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux $ cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" Previously I had an Ubuntu Gutsy i386 install and never showed such issues. The system has 2Gb of RAM and does not run any non-default software. What can I do or how should I debug the problem in order to find out the root cause ? ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- [Gutsy] kernel runs out of memory: Out of memory / invoked oom-killer https://bugs.launchpad.net/bugs/162854 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337470] Re: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure
Problem is still present in Ubuntu Lucid 10.04 (up-to-date), with the very same symptoms: the DVD live image appears to survive suspends but the HDD installed image hangs upon resuming from suspend. I have also tried with and without the acerhk driver (used for the Wireless LED / software rfkill) -- no difference. My wlan card is: 08:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) @Andy / @Leann: it's been over one year and over 3 Ubuntu releases since this has been reported (by me and many other people) -- can we have someone assigned to the bug or at least properly triaged ? My best guess is that there is an inconvenient ACPI default setting which upsets the BIOS/power management on these notebook models. Thank you ! -- [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure https://bugs.launchpad.net/bugs/337470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550133] Re: gs crashed with SIGSEGV in gx_bits_cache_alloc()
Same situation -- priting from Google Chrome (or from PDF generated from it) fails, from FireFox it's alright. Probably duplicate of #440280 -- gs crashed with SIGSEGV in gx_bits_cache_alloc() https://bugs.launchpad.net/bugs/550133 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440280] Re: gs crashed with SIGSEGV in gx_bits_cache_alloc()
I'm affected by the same bug in Ubuntu 10.04 (up-to-date), with a HP LJ M1522nf networked printer -- printing from Chrome or the PDF generated from Chrome fails, the same page from Firefox works. Test page works. -- gs crashed with SIGSEGV in gx_bits_cache_alloc() https://bugs.launchpad.net/bugs/440280 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337470] Re: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure
Checked again in Ubuntu 10.10 (Maverick Meerkat) and observed the same abnormal behavior: while running from the LiveCD suspend appears to be working to be fine but as soon as it's installed on the machine's HDD suspending will break. I have also tried the following testcase scenario: running from the LiveCD, left an fsck running on a big partition and tried suspending and then resuming. Result: working flawless, the fsck process has been running both pre-suspend and post-resume. I guess the SATA controller/HDD is out of the question now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/337470 Title: [FUJITSU SIEMENS AMILO Li 2735] suspend/resume failure -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
