[Bug 1158982] Re: SD card inaccesible: mmc0: error -110 whilst initialising SD card
I was facing the same problem with 3.8, updated to 3.9 but its exactly the same: dmesg: [ 3219.307280] mmc0: card e624 removed [ 3456.883573] mmc0: error -110 whilst initialising SD card [ 3458.295000] mmc0: error -110 whilst initialising SD card [ 3459.706588] mmc0: error -110 whilst initialising SD card lspci -v 13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) Subsystem: Hewlett-Packard Company Device 1657 Flags: bus master, fast devsel, latency 0, IRQ 50 Memory at c350 (32-bit, non-prefetchable) [size=4K] Expansion ROM at c240 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-00-00-01-00-4c-e0-00 Kernel driver in use: rtsx_pci Tried with a SDHC Class 10 (Sandisk) and a Micro SD adapter, both give the same error! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158982 Title: SD card inaccesible: mmc0: error -110 whilst initialising SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058518] Re: package transmission-daemon 2.51-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
I'm using transmission-d 2.76-0 and have the same exact problem is this "fixable"? Is there any workaround? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058518 Title: package transmission-daemon 2.51-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1058518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058518] Re: package transmission-daemon 2.51-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Please note that changing the user makes no difference to me, in fact mine is "debain-trasmission" sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up transmission-daemon (2.76-0ubuntu0.12.10.1) ... * Starting bittorrent daemon transmission-daemon /usr/bin/transmission-daemon already running. invoke-rc.d: initscript transmission-daemon, action "start" failed. dpkg: error processing transmission-daemon (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: transmission-daemon E: Sub-process /usr/bin/dpkg returned an error code (1) I also noticed this: * Restarting bittorrent daemon transmission-daemon [18:42:03.798] Couldn't read "/home/miguelc/.config/user-dirs.dirs": Permission denied Which makes no sense and nothing in the config file points to miguelc "user" not even the download "dirs" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058518 Title: package transmission-daemon 2.51-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1058518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975683] [NEW] after upgrading to 11.10 I tried to update. I got a message that it can't install ubuntu-desktop
Public bug reported: Running a dual boot with Windows 7 on a 64-bit system. Was using Zorin Linux. After upgrade, I received the message above. Unable to install ubuntu desktop. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: update-manager 1:0.152.25.8 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 6 21:45:55 2012 InstallationMedia: Zorin OS 5.2 64bit - Release amd64 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG= SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to oneiric on 2012-04-07 (0 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975683 Title: after upgrading to 11.10 I tried to update. I got a message that it can't install ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/975683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975683] Re: after upgrading to 11.10 I tried to update. I got a message that it can't install ubuntu-desktop
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975683 Title: after upgrading to 11.10 I tried to update. I got a message that it can't install ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/975683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73992] Re: Could not install '/var/cache/apt/archives/hotkey-setup_0.1-17ubuntu3_i386.deb'
Hello, I've encountered this same problem. Here's the error message I get: --- Could not install '/var/cache/apt/archives/hotkey-setup_0.1-17ubuntu3_i386.deb' The upgrade aborts now. Please report this bug against the 'update- manager' package and include the files in /var/log/dist-upgrade/ in the bugreport. subprocess new pre-removal script returned error exit status 1 I'll attach dist-upgrade as directed above. Please let me know if anyone needs more info. ** Attachment added: "log files from dist-upgrade" http://librarian.launchpad.net/5493316/dist-upgrade.tar.bz2 -- Could not install '/var/cache/apt/archives/hotkey-setup_0.1-17ubuntu3_i386.deb' https://launchpad.net/bugs/73992 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37876] Re: Kernel does not read DVDs, no automount
I'm going to attempt to summarize the bug's info to date. Based on above comments in the thread: This bug is believed a REGRESSION between Ubuntu 6.06 and the previous release 5.10. The problem is that some written DVDs (but not all) can be read under other OSes, and in fact, Breezy (5.10), but not in Ubuntu Dapper (6.06). Some users have reported success with Kubuntu Dapper (6.06) as well. It is confirmed there is a problem that is preventing certain users from reading certain DVD discs on certain drives. What the problem is, and what is causing it, is unknown or unconfirmed. AFAIK, Reading DVDs isn't performed in user-space, it is done in the kernel. Therefore, a FIRST STEP to troubleshooting would to see if running under a *user-built kernel* built with kernel-package configured with the required DVD-reading options (notably, device support, either IDE, SCSI, or whatever your drive needs, as well as ISO9660 and UDF file system support) works. If it does, then the kernel-building system and the kernel-builders' policies need to be revised. Maybe the archives for the mailing list for the kernel team (if any) or the wiki or whatever need to be consulted to see if they knew and if there was reason. It might also help to see if this regression appeared in the upstream vanilla Linux kernel; although I assume if the config was done right, it should work, since I can burn from my custom 2.6.17 kernel on my Debian box (the other one). This would mainly be of note if upstream vanilla (or someone else) dropped drivers for certain disc drives. Additional info that may help: A user with access to similar (preferably identical) or dual/triple/quad-boot system with Windows (presumably/preferably XP; other versions' support are reported flaky, and Vista is in beta), Ubuntu Dapper (6.06), Breezy (5.10), Kubuntu Dapper (6.06), or a combination of the four, one of which is Ubuntu Dapper, to burn DVDs under Windows, Breezy, and Dapper, and see which ones are readable under which systems. Debian unstable or another system may also be a useful benchmark if available. (The above reports seem inconsistent, so a unified report on all the same hardware would show whether or not this is a software problem. Also, if it shows Dapper can read all DVDs except for those produced by Dapper (and maybe Debian Unstable), then it means there is a problem in the burning software -- my first hunch would to be to look for bugs/regressions or incompatabilities in growisofs/dvd+rw-tools, maybe in OPC or similar. The changelog for said program may help.) Further info that may help: A diff between the configs of the different kernel images for Dapper and Breezy. Assuming the report that the bug doesn't affect Kubuntu Dapper is true, a diff of the configs for the kernel image in Kubuntu versus Ubuntu would also help. (If, for example, by chance, the Dapper kernel has UDF file system support as modular (or omitted) where Breezy/Kubuntu didn't/doesn't, loading (via modprobe or similar) the module, if one was built, might help.) -- Kernel does not read DVDs, no automount https://launchpad.net/bugs/37876 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104535] Re: Default HD power management settings will kill drive
I am also experiencing this issue on my Dell Inspiron 6400. According to smartctl, my load cycle count is 73,603. Now, I’ve had my 6400 for five months, so that’s ~484 cycles per day. At this rate my hard drive (HTS721010G9SA00) will “last” ~3.5 years. -- Default HD power management settings will kill drive https://bugs.launchpad.net/bugs/104535 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 59695] Re: default value in power.sh potentially kills laptop disks
I am also experiencing this issue on my Dell Inspiron 6400. According to smartctl, my load cycle count is 73,603. Now, I’ve had my 6400 for five months, so that’s ~484 cycles per day. At this rate my hard drive (HTS721010G9SA00) will “last” ~3.5 years. -- default value in power.sh potentially kills laptop disks https://bugs.launchpad.net/bugs/59695 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 85974] Crazy OO.o depends in Ubuntu Edgy 6.10
Public bug reported: >From a clean install from 6.10 LiveCD, attempting to remove OpenOffice.org through package management indicates that removing OO.o will also remove "Ubuntu Desktop". Please be aware for next LiveCD release. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Crazy OO.o depends in Ubuntu Edgy 6.10 https://launchpad.net/bugs/85974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57413] Re: Crash on "clear_console"
Here's my crash report attachment. ** Attachment added: "Here's my crash report attachment." http://librarian.launchpad.net/5689014/_usr_bin_clear_console.1000.crash -- Crash on "clear_console" https://launchpad.net/bugs/57413 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102532] Re: k3b does not run in gnome ubuntu
I also have this problem, with an identical message in Terminal. Starting a KDE session fails before any modules load with a message relating to DCOPserver error. Ubuntu 7.04 fully up to date. -- k3b does not run in gnome ubuntu https://bugs.launchpad.net/bugs/102532 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 55739] Re: No more mouse events after using rdesktop
*** This bug is a duplicate of bug 41301 *** https://bugs.launchpad.net/bugs/41301 I have the same problem I get constant messages in /var/log/messages Aug 11 07:47:25 cryptonite kernel: [56108.792815] psmouse.c: bad data from KBC - timeout Aug 11 07:51:51 cryptonite kernel: [56374.595857] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.596956] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.598022] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.599108] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.608842] psmouse.c: GlidePoint at isa0060/serio1/input0 - driver resynched. How I have managed to deal with it is to make sure I open a terminal window on one of my desktops and just unloading and reloading the driver, which get's everything working right again. It's a lot better then reloading X or rebooting. It happens mostly in Firefox, but I have noticed it in other apps as well. It would be nice if there was an update from ubuntu since there seems to be a lot of people having the same problem. modprobe -r psmouse modprobe psmouse Platform info: Sony Vaio VGN-SZ340P Linux cryptonite 2.6.28-15-generic #48-Ubuntu SMP Wed Jul 29 08:54:56 UTC 2009 i686 GNU/ -- No more mouse events after using rdesktop https://bugs.launchpad.net/bugs/55739 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 41301] Re: Mouse clicks stop working sporadically
I have the same problem I get constant messages in /var/log/messages Aug 11 07:47:25 cryptonite kernel: [56108.792815] psmouse.c: bad data from KBC - timeout Aug 11 07:51:51 cryptonite kernel: [56374.595857] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.596956] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.598022] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.599108] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Aug 11 07:51:51 cryptonite kernel: [56374.608842] psmouse.c: GlidePoint at isa0060/serio1/input0 - driver resynched. How I have managed to deal with it is to make sure I open a terminal window on one of my desktops and just unloading and reloading the driver, which get's everything working right again. It's a lot better then reloading X or rebooting. It happens mostly in Firefox, but I have noticed it in other apps as well. It would be nice if there was an update from ubuntu since there seems to be a lot of people having the same problem. modprobe -r psmouse modprobe psmouse Platform info: Sony Vaio VGN-SZ340P Linux cryptonite 2.6.28-15-generic #48-Ubuntu SMP Wed Jul 29 08:54:56 UTC 2009 i686 GNU/ -- Mouse clicks stop working sporadically https://bugs.launchpad.net/bugs/41301 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 807962] Re: unable to find out how to increase Eric4 font size
In: Settings|Preferences|Highlighters|Styles Choose the "Lexer Language" for which you would like to make the change (e.g. Python): Click "All Fonts" Choose the font and size you would like to assign. AFAIK there's no global mechanism to configure fonts for all lexers as once (there's a default, but it's only for unrecognized languages). HTH -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807962 Title: unable to find out how to increase Eric4 font size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/807962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509507] Re: xml file opens in browser
You will find the same behaviour with e.g. json files. This issue was brought up on the mailing list and it is considered "as designed". Basically the project browser (ProjectOthersBrowser _openItem) will only send an "open" event for items where the mime type starts with "text". Previously xml files would have had a text/xml mime type, they are likely now showing up as application/xml (i.e. same problem as application/json). Special casing for application/json and application/xml might be warranted, but as Eric4 is no longer the dev focus I'm not sure it would be likely to go in. HTH -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509507 Title: xml file opens in browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/509507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347592] Re: Eric crash withour error message
This bug is missing any steps to reproduce. What does "compile" mean in the this context? The python file has a syntax error (it just stops in the middle of a triple-quoted string, so I wouldn't expect it to run in Python. Eric doesn't crash loading it for editing. Attempting to do a "Start|Run" in Eric 4.4.18 (current in Kubuntu Precise) simply reports that the syntax error exists in the dialog. BTW, I'm not sure, but I believe it's customary to have *others* mark a bug confirmed when they are able to reproduce it (you may be reporting this bug for someone else, of course, in which case it might be expected). ** Changed in: eric (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/347592 Title: Eric crash withour error message To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/347592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889766] Re: Program unresponsive while editing
This is most likely the autocomplete module in QScintilla. Recommend using the Eric Assistant plugin's autocomplete. See Eric mailing list for a long discussion of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889766 Title: Program unresponsive while editing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/889766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174278] Re: REGRESSION: "failed to allocate video resources" with latest fglrx
This bug also affects Dell Inspiron 15R laptops (Ubuntu Certified Hardware for 12.04) when updated to 13.04. The machine winds up at a text-only console, so the user experience is rather poor. Latest Beta drivers from AMD + explicitly installing the qauntal libudev0 and xserver-xorg-video-intel brings the machine up correctly (as in http://askubuntu.com/questions/205112/how-do-i-get-amd-intel- hybrid-graphics-drivers-working/288355#288355). Would it be reasonable to declare a dependency on those explicit versions of the conflicting packages in the fglrx-installer package? Having people's laptops that have a very common hardware configuration (dual mode AMD/Intel graphics) turn console-only on upgrade seems a bit problematic. Alternately, running "amdconfig --px-igpu" if the condition is detected (lspci has both Intel and AMD VGA drivers and the newer xorg-server- intel and libudev0 packages are installed) might be a workaround, preferably with a user-visible warning of some type. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174278 Title: REGRESSION: "failed to allocate video resources" with latest fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1174278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161315] Re: Eric segmentation fault
I've updated the ubuntu/eric bzr repo with eric 4.5.13 and proposed a merge back into lp:ubuntu/eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161315 Title: Eric segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/1161315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318103] Re: Error importing Python module pocketsphinx
These errors (PyCapsule errors) can be fixed by re-running the Cython generation with a more recent Cython. Not sure whether that should be happening at the Ubuntu or upstream level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318103 Title: Error importing Python module pocketsphinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pocketsphinx/+bug/1318103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277554] [NEW] Incorrect parsing of ip/iface in config files
Public bug reported: Hi there, The version of arno-iptables-firewall on Ubuntu 12.04 (Lucid) 2.0.0 has a bug that manifests when using vlan-tagged interfaces with individual interfaces allowing particular ports, for instance, the configuration: DC_EXT_IF="eth1 eth2.3 " DC_EXT_IF_DHCP_IP=1 # 22, 80, 443 and 161 (SNMP) should only be on the management interface(s) DC_OPEN_TCP="eth1#22 eth1#80 eth1#443 eth1#161 eth2.3#22 eth2.3#80 eth2.3#443 eth2.3#161 " DC_OPEN_UDP="eth1#8000 eth1#161 eth2.3#8000 eth2.3#161 " DC_INT_IF="eth0 " DC_NAT=1 DC_INTERNAL_NET="198.51.100.0/24" DC_NAT_INTERNAL_NET="198.51.100.0/24" DC_OPEN_ICMP=1 RP_FILTER=0 will produce errors on loading, as the eth2.3#22 (and the rest) will all be mis-recognized as ip addresses instead of interfaces. This can be fixed by patching the firewall "environment" file (share/arno-iptables- firewall/environment) with the attached context diff. To test the patch, source the environment file and run: $ source environment $ get_ifs eth2.3#22 + $ get_ips eth2.3#22 eth2.3 $ source new-environment $ get_ifs eth2.3#22 eth2.3 $ get_ips eth2.3#22 0/0 the version of arno in 12.04 is 2.0.0c vs the current 2.0.1 release, so I expect this won't be all that useful upstream, but it would be nice to have a fix for 12.04 servers. I've sent a message to the upstream user's list with the patch as well, in case they wish to release a point revision of 2.0.0. ** Affects: arno-iptables-firewall (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Patch to the share/arno-iptables-firewall/environment file to fix the bug" https://bugs.launchpad.net/bugs/1277554/+attachment/3972577/+files/arno-vlan-parsing.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277554 Title: Incorrect parsing of ip/iface in config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arno-iptables-firewall/+bug/1277554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277554] Re: Incorrect parsing of ip/iface in config files
Ubuntu (server) version is 12.04 (which is *Precise*, not Lucid)... obviously not enough coffee yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277554 Title: Incorrect parsing of ip/iface in config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arno-iptables-firewall/+bug/1277554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378928] Re: Resume on Thinkpad W500 (Radeon HD3650, fglrx) gives black screen
This machine suspends/resumes correctly under Karmic release candidate. Can likely close this ticket now. -- Resume on Thinkpad W500 (Radeon HD3650, fglrx) gives black screen https://bugs.launchpad.net/bugs/378928 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 1682704] [NEW] nvme controller is down will reset (regression in zesty on XPS laptop)
Public bug reported: I've just upgraded a Dell XPS 15" (9550, early 2016 model) with a Samsung NVME drive. Machine was stable under Kubuntu 16.10 with the same drive. After the upgrade to Zesty I've now seen 3 hard lockups (machine loses root fs) with the following message printed: nvme controller is down will reset there are also messages printed to the virtual console reporting failure to write to the underlying disk from the home-directory encfs. Linux tass 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 17.04 (Kubuntu) dmesg about nvme: [1.748864] nvme nvme0: pci function :04:00.0 [1.864553] nvme0n1: p1 p2 p3 p4 p5 p6 [2.961181] EXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. Opts: (null) [4.172546] EXT4-fs (nvme0n1p6): re-mounted. Opts: errors=remount-ro NVME cli shows 57 errors in the error-log, all seeming to be invalid field or invalid namespace. Not sure if that's since boot or since machine creation. Smartctrl shows... smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.10.0-19-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: PM951 NVMe SAMSUNG 512GB Serial Number: S29PNXAH142328 Firmware Version: BXV77D0Q PCI Vendor/Subsystem ID:0x144d IEEE OUI Identifier:0x002538 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Utilization:365,503,283,200 [365 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Thu Apr 13 23:21:32 2017 EDT Firmware Updates (0x06):3 Slots Optional Admin Commands (0x0017): Security Format Frmw_DL *Other* Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.00W --0 0 0 05 5 1 + 4.20W --1 1 1 1 30 30 2 + 3.10W --2 2 2 2 100 100 3 - 0.0700W --3 3 3 3 5005000 4 - 0.0050W --4 4 4 4 2000 22000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02, NSID 0x) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 50% Percentage Used:0% Data Units Read:2,724,346 [1.39 TB] Data Units Written: 6,568,756 [3.36 TB] Host Read Commands: 52,921,997 Host Write Commands:157,530,880 Controller Busy Time: 1,349 Power Cycles: 831 Power On Hours: 5,358 Unsafe Shutdowns: 46 Media and Data Integrity Errors:0 Error Information Log Entries: 57 Error Information (NVMe Log 0x01, max 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSIDVS 0 57 0 0x0004 0x4016 0x0000 1 - 1 56 0 0x0004 0x4016 0x0000 1 - 2 55 0 0x0004 0x4016 0x0000 1 - 3 54 0 0x0004 0x4016 0x0000 1 - 4 53 0 0x0004 0x4016 0x0000 1 - 5 52 0 0x0004 0x4016 0x0000 1 - 6 51 0 0x0004 0x4016 0x0000 1 - 7 50 0 0x0004 0x4016 0x0000 1 - 8 49 0 0x001f 0x4004 0x0000 0 - 9 48 0 0x001e 0x4004 0x0000 0 - 10 47 0 0x001f 0x4004 0x0000 0 - 11 46 0 0x001e 0x4004 0x0000 0 - 12 45 0 0x001f 0x4004 0x0000 0 - 13 44 0 0x001e 0x4004 0x0000 0 - 14 43 0 0x 0x4016 0x0000 1 - 15 42 0 0x0004 0x4016 0x0000 1 - ... (41 entries not shown) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682704 Title: nvme controller is down will reset (regression in zesty on XPS laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/168
[Bug 1682704] Re: nvme controller is down will reset (regression in zesty on XPS laptop)
*** This bug is a duplicate of bug 1678184 *** https://bugs.launchpad.net/bugs/1678184 Thim Thom you can work around the problem by editing the GRUB command- line in /etc/default/grub ``` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nouveau.modeset=0 nvme_core.default_ps_max_latency_us=6000" ``` and then running `update-grub` and rebooting. There is a link to the duplicate bug above which includes this work-around, though you have to read the comments to see it. Apparently there's a fix in the kernel pending, but I haven't actually tried disabling the flag to see if it's fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682704 Title: nvme controller is down will reset (regression in zesty on XPS laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497326] Re: grub-reboot does not restore previous default after reboot
I see that this bug has been reported as fixed, however the bug still seems present on Lucid with the latest stable updates. Is this fix planned to be released in a software update any time soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/497326 Title: grub-reboot does not restore previous default after reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788298] [NEW] grub-reboot changes boot default permanently on Lucid LTS
Public bug reported: Binary package hint: grub-pc This is related to the following bug: https://bugs.launchpad.net/ubuntu/karmic/+source/grub2/+bug/497326 Opening a new bug since the aforementioned bug is related to Karmic. Although it was marked as "fixed" over 16 months ago, this feature still appears to be broken in Lucid LTS. Ubuntu Release: Ubuntu 10.04.2 LTS Architecture: x86_64 Package Version: 1.98-1ubuntu10 Steps taken: - Edited /etc/boot/default and changed "GRUB_DEFAULT=0" to "GRUB_DEFAULT=saved" - Used grub-reboot so that grub would reboot into Windows on the next boot only - Rebooted from Ubuntu - Windows booted as expected - Rebooted from Windows Expected Results: - After rebooting from Windows, my grub default selection should be back to Ubuntu (or whatever it was before issuing grub-reboot) since grub-reboot is supposed to "set the default boot entry for GRUB, for the next boot only" as per the man page. Actual Results: - Windows remains selected by default at the bootloader screen and boots. Note that this prevents users from being able to reboot into Windows and back when they are accessing their machines remotely. Additional Information: - The system I am experiencing this on is set up as follows: - Ubuntu is installed on a Linux mdadm raid 1 mirror (/dev/sda1 and /dev/sdb1) - Windows is installed on an Intel Raid 1 mirror (what would have been /dev/sdc and /dev/sdd are now /dev/mapper/isw_febcbhicb_Windows) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: grub-pc 1.98-1ubuntu10 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CheckboxSubmission: 60d09ed5715e10eba06ad43865289d68 CheckboxSystem: f134069bba098730d27f59b402920826 Date: Wed May 25 15:08:12 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: grub2 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug grub2 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788298 Title: grub-reboot changes boot default permanently on Lucid LTS -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788298] Re: grub-reboot changes boot default permanently on Lucid LTS
** Attachment added: "/etc/default/grub" https://bugs.launchpad.net/bugs/788298/+attachment/2142670/+files/grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788298 Title: grub-reboot changes boot default permanently on Lucid LTS -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497326] Re: grub-reboot does not restore previous default after reboot
Hello, Thanks for the response. I opened a new bug report a few days ago. Here's the link: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/788298 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/497326 Title: grub-reboot does not restore previous default after reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788298] Re: grub-reboot changes boot default permanently on Lucid LTS
It appears that this bug may not actually be related to bug #497326 as per the recent update in that thread. Perhaps this has more to do with the disk configuration that's being used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788298 Title: grub-reboot changes boot default permanently on Lucid LTS -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692640] [NEW] python-profiler fails to install if Python 2.7 is not installed
Public bug reported: Binary package hint: python-profiler The package attempts to run the Python 2.7 variant of py_compile.py, which doesn't exist until the python2.7 package is installed. This caused a Maverick upgrade to fail, as the python-profiler package was installed and the failure killed the whole upgrade process. Work-around is simply to install Python2.7, but the package should check for the existence of py_compile.py before attempting to run it. ** Affects: python-profiler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692640 Title: python-profiler fails to install if Python 2.7 is not installed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497326] Re: grub-reboot does not restore previous default after reboot
This bug appears in Lucid LTS with grub-pc - 1.98-1ubuntu9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/497326 Title: grub-reboot does not restore previous default after reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 616158] Re: Crash on selection of empty 3rd drive of 3
Afraid that server is no longer available to test. If you've checked the array bounds feel free to close the ticket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/616158 Title: Crash on selection of empty 3rd drive of 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/616158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577044] [NEW] Crash-in-resume after suspend leaves network disabled
Public bug reported: Binary package hint: pm-utils Closing laptop lid on a Lenovo W500 running Kubuntu Lucid (10.04 LTS) causes a suspend/resume cycle. As the resume often crashes, the machine must often be manually killed (hard power off) and restarted. When this is done, the network does not resume (KDENetworkManager reports the networking as unmanaged). The only way I've found to restore it so far is to attempt another suspend/resume cycle (which may or may not require another hard reboot). Likely on startup the suspend/resume config/setting which disables networking during suspend/resume should be cleared out. Mostly just a nuisance, as we know not to intentionally suspend the machine, but it's definitely annoying. ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- Crash-in-resume after suspend leaves network disabled https://bugs.launchpad.net/bugs/577044 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 289925] Re: Segmentation fault on amd64 in glutInitDisplayMode()
This bug was fixed for the 3.0.1 release by disabling GL error-checking on GLUT functions. This is another case of (some) newer GL implementations being extremely anal about calls to GL entry points before there is a GL context. Basically the glGetError() calls were seg-faulting because GLUT didn't have a context set up yet. -- Segmentation fault on amd64 in glutInitDisplayMode() https://bugs.launchpad.net/bugs/289925 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 537851] [NEW] dhclient silently ignores unreadable config-file
Public bug reported: When running dhclient against a config-file that happens not to be whitelisted by app-armour, dhclient will silently ignore the failure and continue with the default config-file in /etc/dhcp3/dhclient.conf rather than error out. dhclient should (at least) report an error/warning on stdout, and should likely exit with a non-zero error code when an explicitly-passed config-file is not readable. That is, if the user has *explicitly* specified a config on the command-line, no config other than that config should be used. To reproduce/test, create a dhclient.conf file anywhere that isn't readable/writable by the app-armour profile (such as ~/) with a non- standard option specified (one that is not in your /etc/dhcp3/dhclient.conf): send vendor-class-identifier "myvendorname"; and attempt to run: $ sudo dhclient -cf ~/dhclient.conf -lf /var/lib/dhcp3/test.leases eth0 while running wireshark for eth0. dhclient will silently ignore the failure to load ~/dhclient.conf and will instead use /etc/dhcp3/dhclient.conf (you can see this in your wireshark dump, as vendor-class-identifier will not be sent). Move the same file to /etc/dhcp3/dhclient-test.conf and run again and you should see the option being sent. Description:Ubuntu 9.10 Release:9.10 Package: dhcp3-client State: installed Automatically installed: no Version: 3.1.2-1ubuntu7.1 ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhclient silently ignores unreadable config-file https://bugs.launchpad.net/bugs/537851 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 616158] [NEW] Crash on selection of empty 3rd drive of 3
Public bug reported: Binary package hint: ubiquity With version 2.2.25 of ubiquity and ubiquity-frontend-kde see the following error: {{{ Traceback (most recent call last): File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartAuto.py", line 259, in on_extra_combo_changed self.extra_bar_frames[index].setVisible(True) IndexError: list index out of range }}} when attempting to choose the 3rd of 3 hard-drives as the installation target. Note, this is *not* the ubiquity-frontend-kde version on the livecd by default (which also crashes), I did an aptitude install ubiquity ubiquity-frontend-kde in hopes that it had been fixed. I'd mark this a blocker as I can't install the OS on the disk to which I need to install it. Similar bugs: #601238 Installer crashes on selecting hard drive (appears identical from the traceback, but my drives are just simple drives) #485450 installer crashes after i choose my secondary HD as the one for the installation (different traceback here, and presumably fixed in my later version) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- Crash on selection of empty 3rd drive of 3 https://bugs.launchpad.net/bugs/616158 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 616158] Re: Crash on selection of empty 3rd drive of 3
** Attachment added: "Syslog" http://launchpadlibrarian.net/53458598/syslog -- Crash on selection of empty 3rd drive of 3 https://bugs.launchpad.net/bugs/616158 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 616158] Re: Crash on selection of empty 3rd drive of 3
** Attachment added: "Partman log" http://launchpadlibrarian.net/53458616/partman -- Crash on selection of empty 3rd drive of 3 https://bugs.launchpad.net/bugs/616158 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 616158] Re: Crash on selection of empty 3rd drive of 3
Further to this. Disabling the other two drives caused the installer to show no drives at all on the partitioning stage. Moving the drive to the first SATA port on the machine caused it to show up in the drive list and partition/install correctly. It is possible that the original crash was related to the drive originally being on the 3rd SATA bus (i.e. #5 of 6 SATA connectors). -- Crash on selection of empty 3rd drive of 3 https://bugs.launchpad.net/bugs/616158 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 289925] Re: Segmentation fault on amd64 in glutInitDisplayMode()
It seems like we have something like the following: * race condition where native drivers are fast enough not to crash (i.e. they are filling out an internal structure before the call to glutInit) * use of a GL operation by FreeGLUT that requires a GL context under MESA, but does not under the proprietary drivers * use of a MESA operation that is buggy in software but correct in the common hardware implementations I'll try again to reproduce the effect on my Ubuntu machine. -- Segmentation fault on amd64 in glutInitDisplayMode() https://bugs.launchpad.net/bugs/289925 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 289925] Re: Segmentation fault on amd64 in glutInitDisplayMode()
Okay, on my Jaunty AMD64 I cannot replicate the problem even when I switch to MESA software renderer (it doesn't occur with fglrx driver either). However, looking through the tracebacks posted, it seems pretty obvious that some configurations are failing when a call to glGetError happens before the GL has a context. There's nothing in the docs which says that should ever cause a failure (let alone a segfault), so it seems we're looking at a broken implementation issue. We could work around it by disabling GLUT error checking entirely, but that seems a bit of a nuclear option, as it would change the API. Instead I'm thinking we'll disable error checking *just* for the GLUT functions commonly called before the GLUT context is created. I've checked in changes to bzr head to implement this. Please do the following and report whether the bug is fixed for you: bzr branch lp:pyopengl # add pyopengl/OpenGL to your PYTHONPATH then run the test script. -- Segmentation fault on amd64 in glutInitDisplayMode() https://bugs.launchpad.net/bugs/289925 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 378928] [NEW] Resume on Thinkpad W500 (Radeon HD3650, fglrx) gives black screen
Public bug reported: Binary package hint: pm-utils This may be a duplicate of #378400 and is similar to #285909 (but with different video card). Suspend appears to work correctly. Resume works properly save for the display. Screen remains unlit and unresponsive in almost all tests. In a few rare cases the resume works correctly (appears to be basically random, though the difficulty of reproducing makes it hard to say). SSH into the machine after resume works correctly and all seems to be well, save that the video card seems to be running full-out (causing the machine to overheat rather dramatically). Have attempted enabling s3 bios quirk modes in HAL configuration without any change in symptoms and have tried with quirk-vbe-post both enabled and disabled, with the same result. Machine was suspending/resuming reliably under Kubuntu Intrepid (this is now Kubuntu Jaunty) using the fglrx driver. Description:Ubuntu 9.04 Release:9.04 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: fglrx Package: pm-utils 1.2.2.4-0ubuntu4 PackageArchitecture: all ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils Uname: Linux 2.6.28-11-generic x86_64 ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Resume on Thinkpad W500 (Radeon HD3650, fglrx) gives black screen https://bugs.launchpad.net/bugs/378928 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 378928] Re: Resume on Thinkpad W500 (Radeon HD3650, fglrx) gives black screen
** Attachment added: "Suspend/resume failure log" http://launchpadlibrarian.net/27004905/pm-suspend.log ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27004906/Dependencies.txt -- Resume on Thinkpad W500 (Radeon HD3650, fglrx) gives black screen https://bugs.launchpad.net/bugs/378928 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 289925] Re: Segmentation fault on amd64 in glutInitDisplayMode()
I'm fine with a higher priority, but as of yet I have no reproducibility. As a check, can someone do: import OpenGL OpenGL.ERROR_CHECKING = False in one of their test scripts? That might at least tell me whether it's really the glGetError call causing the problem or whether that just happens to show up in the error reports. *Pyglet* showing the problem is just *weird*, there's no common code between pyglet and PyOpenGL other than ctypes and Python. If we have a problem there we're looking at a methodology failure or a problem with ctypes/Python. -- Segmentation fault on amd64 in glutInitDisplayMode() https://bugs.launchpad.net/bugs/289925 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 333944] Re: Kubuntu jaunty: kded4 at 100% of CPU load
Also seeing this on both of our machines, both upgraded from Intrepid to Jaunty this afternoon. Both were updated using the cdromupdate method from alternate CDs. One with internet package updates, the other without. * Lenovo W500 (ATI Radeon HD 3650 (fglrx driver), Intel Core 2 Duo) * Custom-built (Athlon X2 4800, nVidia GeForce 7600 GS (proprietary driver)) If I add a few standard widgets to the desktop even a single account takes 100% of both CPUs. kde4d always seems to take 100% of one CPU for each logged in user, plasma goes up to 100%. Xorg process is not showing any particularly high load (~2%). Enabling "desktop effects" (compiz) does not change CPU usage. One machine (Lenovo) is rather unstable (multiple plasma crashes), but that's likely because it's getting to 73 deg Fahrenheit due to the overloading if there's anything else running on the machine. It's up to 63 deg with just the one CPU pegged. The machines are rendered unusable, so I would suggest we may need a slightly higher priority than "low". The referenced kdelibs bug does not appear to be relevant, as I'm not AFAIK using kget (though I suppose one of the widgets might have used it). >From the Lenovo's Xorg.0.log: (WW) Falling back to old probe method for fglrx (II) ATI Proprietary Linux Driver Version Identifier:8.60.40 (II) ATI Proprietary Linux Driver Release Identifier: 8.60.4 (II) ATI Proprietary Linux Driver Build Date: Mar 14 2009 21:46:40 (II) Loading PCS database from /etc/ati/amdpcsdb (WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0 (WW) Video driver ABI version of the X server is 5.0 ... (II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906 (WW) fglrx(0): could not detect X server version (query_status=-1) Don't seem to be any relevant Errors or Warnings in the AMD's Xorg.0.log. GDB connect backtrace on the Lenovo: #0 0x7f482a61b1c0 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0 #1 0x7f48289bdb1c in xcb_poll_for_reply () from /usr/lib/libxcb.so.1 #2 0x7f482d13b80f in ?? () from /usr/lib/libX11.so.6 #3 0x7f482d13c345 in _XEventsQueued () from /usr/lib/libX11.so.6 #4 0x7f482d124ed3 in XEventsQueued () from /usr/lib/libX11.so.6 #5 0x7f482e5b3e5c in ?? () from /usr/lib/libQtGui.so.4 #6 0x7f4829a7ced2 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #7 0x7f4829a7d7c9 in ?? () from /usr/lib/libglib-2.0.so.0 #8 0x7f4829a7da7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0x7f482d99be6f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #10 0x7f482e5b3c9f in ?? () from /usr/lib/libQtGui.so.4 #11 0x7f482d971002 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #12 0x7f482d9713cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #13 0x7f482d973694 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #14 0x7f4830200cd7 in kdemain () from /usr/lib/libkdeinit4_kded4.so #15 0x7f482bdc55a6 in __libc_start_main () from /lib/libc.so.6 #16 0x00400759 in _start () -- Kubuntu jaunty: kded4 at 100% of CPU load https://bugs.launchpad.net/bugs/333944 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 333944] Re: Kubuntu jaunty: kded4 at 100% of CPU load
Just tried logging out and back in on both machines. The 100% usage of one CPU is no longer occurring (CPU is down in the low single percentages). Have added back all of the widgets that were creating a full load on both processors and still seeing just a 20% (or so, fluctuates rapidly) load from kwin, plasma or xorg. Maybe the problem was related to the plasma crashes winding up creating multiple queues that were each polling. Anyway, if this works for others it may be that we really are looking at a low-priority ticket. -- Kubuntu jaunty: kded4 at 100% of CPU load https://bugs.launchpad.net/bugs/333944 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 746508] Re: apt-check uses too much resources (starts too many processes)
To be clear, this bug causes the Wily machine to hard-crash with 100% CPU and 100% memory usage, forcing a hard reboot. Can't log in at console to restart, can't even get to a console to run killall. So every few days the system becomes a paper-weight and has to be converted back into a computer by human interaction... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746508 Title: apt-check uses too much resources (starts too many processes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/746508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs