[Bug 1824891] [NEW] ever since updating to 18.04 ethernet keeps resetting several times per second
Public bug reported: Ever since I updated this system to 18.04, the ethernet has been resetting several times per second. /var/log/syslog looks like this fairly rapidly. It makes updating awkward. I have to keep restarting the update because it keeps complaining intermittently about being unable to contact the repository, but the system is currently up to date as of a few minutes ago. syslog looks like this: Apr 15 16:00:30 notebook kernel: [42489.401932] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex Apr 15 16:00:31 notebook kernel: [42490.810245] atl1 :02:00.0: enp2s0 link is down Apr 15 16:00:31 notebook kernel: [42490.819643] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex Apr 15 16:00:32 notebook kernel: [42491.281258] atl1 :02:00.0: enp2s0 link is down Apr 15 16:00:32 notebook kernel: [42491.286405] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex Apr 15 16:00:33 notebook kernel: [42492.223598] atl1 :02:00.0: enp2s0 link is down Apr 15 16:00:33 notebook kernel: [42492.228567] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex 1) Here is lsb_release -rd: Description:Ubuntu 18.04 LTS Release:18.04 2) apt-cache policy pkgname: NA, as far as I know. 3) What you expected to happen: Ethernet to stay up 4) What happened instead: It keeps bouncing like atrial flutter! kern.log and syslog files are filled from top to bottom with lines like those shown above. Similarly, dmesg -d shows only lines like: [43956.763221 <0.005033>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43957.230123 <0.466902>] atl1 :02:00.0: enp2s0 link is down [43957.235245 <0.005122>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43957.701180 <0.465935>] atl1 :02:00.0: enp2s0 link is down [43957.706210 <0.005030>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43959.115537 <1.409327>] atl1 :02:00.0: enp2s0 link is down [43959.120522 <0.004985>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43959.586944 <0.466422>] atl1 :02:00.0: enp2s0 link is down [43959.591890 <0.004946>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43960.058258 <0.466368>] atl1 :02:00.0: enp2s0 link is down [43960.063293 <0.005035>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43960.529823 <0.466530>] atl1 :02:00.0: enp2s0 link is down [43960.534784 <0.004961>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [43962.415925 <1.881141>] atl1 :02:00.0: enp2s0 link is down [43962.421103 <0.005178>] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex ** Affects: lxdm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg and /var/log/apport*" https://bugs.launchpad.net/bugs/1824891/+attachment/5256077/+files/tarfile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824891 Title: ever since updating to 18.04 ethernet keeps resetting several times per second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1824891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1201134] Re: LXDM logins not being logged in utmp
I don't think the authors consider this a bug. As of 18.04, it's still hardcoded this way. The following is one of two essentially (for your purposes) identical instances: src/lxterminal.c:1252: vte_terminal_fork_command_full( VTE_TERMINAL(term->vte), VTE_PTY_NO_LASTLOG | VTE_PTY_NO_UTMP | VTE_PTY_NO_WTMP, pwd, exec, env, G_SPAWN_SEARCH_PATH | G_SPAWN_FILE_AND_ARGV_ZERO, NULL, NULL, >pid, NULL); Probably, replacing those flags with a zero in both cases would be sufficient for a personal system, although I haven't checked for unanticipated consequences. In my opinion, they should have at least made it an option to configure. I did a quick test just now, of manually zeroing the argument in gdb, which verified that something like the following should work: Probably something like: #if USE_UTMP #define LOG_UTMP VTE_PTY_NO_LASTLOG | VTE_PTY_NO_UTMP | VTE_PTY_NO_WTMP #else #define LOG_UTMP 0 #endif except it only works for root, presumably because before the call to the fork (or spawn) routine, there must be a setuid call that is too early. I hope it's not in the vte library, but I doubt it, if other terminals (such as xterm) do the right thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201134 Title: LXDM logins not being logged in utmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1201134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791309] Re: pcilib: sysfs_read_vpd: read failed: Input/output error
Originally, I had associated my having plugged a Sun Microsystems button-cell powered microphone into the microphone jack with the sudden failure of all ALC882 functionality in an ASUS G2S running 18.04 But I just happened across a mention of the alsa-info.sh script for debugging a similar issue, and upon running it I got the "pcilib: sysfs_read_vpd: read failed: Input/output error" message reported here. The script reported: Your ALSA information is located at http://www.alsa-project.org/db/?f=520faf9e4fd6b1e6a037b7c816ef02b610318e0c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791309 Title: pcilib: sysfs_read_vpd: read failed: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1791309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800888] Re: interfaces repetitively deleted in apparent synchrony with up/down network interface seesawing
Output from: apport-collect 1800888 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=75pw0d303tBwqrdbP96z_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... ERROR: connecting to Launchpad failed: [Errno 13] Permission denied: '/home/mab/.cache/apport/launchpad.credentials' You can reset the credentials by removing the file "/home/mab/.cache/apport/launchpad.credentials" notebook:~ 42 % rm /home/mab/.cache/apport/launchpad.credentials rm: cannot remove '/home/mab/.cache/apport/launchpad.credentials': No such file or directory notebook:~ 43 % Changing to "Confirmed": apport-collect 1800888 failed, per output above. Use the logs in the tar file that "ubuntu kernel bot" claimed wasn't present. Ubuntu bot is the final one of many impediments to submitting reports that your bug process placed in front of me while I was missing sleep while hurdling over each one to get this bug to you. THE final one. I wash my hands of this. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800888 Title: interfaces repetitively deleted in apparent synchrony with up/down network interface seesawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800887] Re: launchpad is claiming my report has one error, but is not flagging what that error is
You may choose to cancel this bug. Or better, you may choose to fix (or at least warn about) the problem I am about to describe. The cause of the difficulty resulted from my having originally entered: "Network Manager and/or ntpd" under "In what package did you find this bug?". The page had flagged that, so per recommendation, I clicked "I don't know instead". However, because I did not erase the words "Network Manager and/or ntpd", when I clicked "Submit", the web page decided that I should have clicked on the button next to the words that I did not erase, so it re- clicked it for me and unclicked "I don't know", which re-introduced the page's recognition that I had made an error. Because I had explicitly clicked "I don't know", it hadn't occurred to me to consider that clicking "Submit" would have caused my most recently chosen answer to the "package" question to have been reverted to my previous answer by the page itself, on my behalf. I had already fixed the error I had made on that part of the page (or so I thought), so when another error was flagged, I looked everywhere else on the page to try to figure out what the page was complaining about. I understand that this may have arisen out of an idiosyncrasy in the implementation, but with that being the case, it would take only a few additional characters of code to detect what it could consider to be an "incomplete change" and provide some warning of its inability to handle the manner in which a human would normally and naturally be expected to correct the error I had originally made and corrected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800887 Title: launchpad is claiming my report has one error, but is not flagging what that error is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800888] [NEW] interfaces repetitively deleted in apparent synchrony with up/down network interface seesawing
Public bug reported: In Description: Ubuntu 18.04.1 LTS Release:18.04 Occasionally an attempt to open a connection fails, or an attempt to transfer a file, or do something else that works by opening a socket fails. Other things that you would expect to proceed normally with an already opened socket continue to do so. That's the case with TCP, at least. One might draw a conclusion based on the log contents described below that it would probably not so be for UDP, but I haven't tried to verify that. Examining syslog reveals groupings of strange repetitive behavior as demonstrated in the 3 successive groups copied from syslog below. I'm not certain of exactly when this behavior first appeared. I don't know if it's related, but since it appeared, I have seen no more instances of a different anomalous interface network interface behavior (namely: the network being unavailable upon system resumption following system suspension, and requiring performance of at least once more system suspension in order to restore network connectivity) The following are the most concise extracts I could make from the logs to demonstrate the issue. See the attachment for more: Oct 31 00:07:57 notebook ntpd[5122]: Deleting interface #124 enp2s0, 192.168.0.215#123, interface stats: received=72, sent=72, dropped=0, active_time=211 secs Oct 31 00:07:57 notebook ntpd[5122]: Deleting interface #125 enp2s0, fe80::540b:bc14:dd5f:304f%2#123, interface stats: received=0, sent=0, dropped=0, active_time=211 secs Oct 31 00:07:57 notebook kernel: [16414.973867] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex Oct 31 00:07:57 notebook NetworkManager[975]: [1540969677.5690] device (enp2s0): carrier: link connected Oct 31 00:07:59 notebook ntpd[5122]: Listen normally on 126 enp2s0 192.168.0.215:123 Oct 31 00:07:59 notebook ntpd[5122]: Listen normally on 127 enp2s0 [fe80::540b:bc14:dd5f:304f%2]:123 Oct 31 00:12:42 notebook kernel: [16699.579883] atl1 :02:00.0: enp2s0 link is down Oct 31 00:12:43 notebook ntpd[5122]: Deleting interface #126 enp2s0, 192.168.0.215#123, interface stats: received=87, sent=88, dropped=0, active_time=284 secs Oct 31 00:12:43 notebook ntpd[5122]: Deleting interface #127 enp2s0, fe80::540b:bc14:dd5f:304f%2#123, interface stats: received=0, sent=0, dropped=0, active_time=284 secs Oct 31 00:12:43 notebook kernel: [16701.175235] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex Oct 31 00:12:43 notebook NetworkManager[975]: [1540969963.7701] device (enp2s0): carrier: link connected Oct 31 00:12:45 notebook ntpd[5122]: Listen normally on 128 enp2s0 192.168.0.215:123 Oct 31 00:12:45 notebook ntpd[5122]: Listen normally on 129 enp2s0 [fe80::540b:bc14:dd5f:304f%2]:123 Oct 31 00:13:09 notebook kernel: [16726.743280] atl1 :02:00.0: enp2s0 link is down Oct 31 00:13:10 notebook ntpd[5122]: Deleting interface #128 enp2s0, 192.168.0.215#123, interface stats: received=20, sent=20, dropped=0, active_time=25 secs Oct 31 00:13:10 notebook ntpd[5122]: Deleting interface #129 enp2s0, fe80::540b:bc14:dd5f:304f%2#123, interface stats: received=0, sent=0, dropped=0, active_time=25 secs Oct 31 00:13:10 notebook NetworkManager[975]: [1540969990.9253] device (enp2s0): carrier: link connected Oct 31 00:13:10 notebook kernel: [16728.330285] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex Oct 31 00:13:12 notebook ntpd[5122]: Listen normally on 130 enp2s0 192.168.0.215:123 Oct 31 00:13:12 notebook ntpd[5122]: Listen normally on 131 enp2s0 [fe80::540b:bc14:dd5f:304f%2]:123 Oct 31 00:16:30 notebook kernel: [16927.574126] atl1 :02:00.0: enp2s0 link is down While not scientific, I suspect the following view of the (brief enough to permit reliable TCP byte streams, as verified by md5sum) timing between "link down" and "link up" events (as opposed to the much longer amount of time elapsing between "link up" and the next down event) might help to explain why the problem is not more symptomatic than it is: [Oct30 20:23] atl1 :02:00.0: enp2s0 link is down [ +1.544088] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [Oct30 20:24] atl1 :02:00.0: enp2s0 link is down [ +1.630772] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [Oct30 20:32] atl1 :02:00.0: enp2s0 link is down [Oct30 20:33] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [Oct30 20:38] atl1 :02:00.0: enp2s0 link is down [ +1.626526] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex [Oct30 20:42] atl1 :02:00.0: enp2s0 link is down [ +1.578927] atl1 :02:00.0: enp2s0 link is up 100 Mbps full duplex As before, this is brief, but enough to be illustrative, and more can be found in the tarred log info. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ethernet frequent-seesawing interface link-down link-up seesawing ** Attachment added: "dmesg,loggreps.tar"
[Bug 1800887] [NEW] launchpad is claiming my report has one error, but is not flagging what that error is
Public bug reported: launchpad is claiming my report has one error, but is not flagging what that error is I would try to enclose the report that it has the problem with, but it would flag that report as having one error, too, without flagging the error itself, so I don't know how to be specific about it. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800887 Title: launchpad is claiming my report has one error, but is not flagging what that error is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767116] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubunt
At their web site, Nvidia is able to detect the specific nvidia GPU present in the current system from the web page. It would thus seem to be reasonable for an nvidia package installation to perfom a similar check during installation, and compare the current GPU against a list of those supported by the software being installed. Unless manually overridden, this could be used to prevent installation of versions of software known to be incompatible with the current GPU from interfering with a separate installation of compatible software. (or to revert steps already performed it if the check could not be performed before changes had already been made) The use of such a check could be prophylactic against bug reports such as this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767116 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1767116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 836250] Re: 8086:4238 [Oneiric] [Regression] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops
I tried iwconfig wlan3 power off (for some reason, my wireless interface is wlan3, not wlan0) but got: # iwconfig wlan3 power off Error for wireless request Set Power Management (8B2C) : SET failed on device wlan3 ; Operation not supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/836250 Title: 8086:4238 [Oneiric] [Regression] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/836250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215624] Re: Philips Semiconductors DVB TV Tuner Card Not Working
The driver at http://powarman.dyndns.org/hgwebdir.cgi/v4l-dvb-saa716x/ reportedly builds and works OK with older releases using linux versions 2.6.24 thru at least 2.6.35, ., but it apparently has dependencies on linux 3.x that keep it from building. I tried compiling it on Oneiric. There were a lot of errors, most resulting from undefined macros such as I2C_CLASS_TV_DIGITAL and T_DIGITAL_TV and from a missing linux header: ( v4l/dvbdev.c:36:28: fatal error: linux/smp_lock.h: No such file or directory ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/215624 Title: Philips Semiconductors DVB TV Tuner Card Not Working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/215624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930350] [NEW] xorg.conf plus emacs causes abrupt logout via Xorg SEGV
Public bug reported: This is in 11.10, but also occurred in 10.10 With nvidia-current (280.x) installed: If there is no xorg.conf, everything is fine. It takes Xorg longer to start up, because it has to load extra drivers (before unloading all but the nvidia driver), but the problem being reported does not occur. But if one creates an xorg.conf (whether with nvidia-xconfig or nvidia- settings, or just by hand), there is a severe stability problem. Immediately upon starting emacs, the Xorg started using that xorg.conf dies with a segmentation fault, causing an abrupt logout. This is not limited to emacs. The same thing happens when starting VirtualBox. Presumably other programs can trigger the SEGV. To reproduce the problem, you just need to be running an Xorg that was started using an xorg.conf that loads the nvidia-current driver(or a related one from the nvidia-260 to nvidia-290 family) and type emacs from a bash prompt. As stated above, the problem only occurs when there is an xorg.conf file. If the same driver is instead loaded via Xorg's heuristics because there was no xorg.conf, then Xorg does not incur the SEGV when emacs starts. The problem does not appear to occur with the legacy nvidia-96 driver still supplied for old GPU's. I do not know whether it occurs with the legacy nvidia-173 driver. I've reproduced it with every incarnation of nvidia-current since nvidia-260. If one had to guess, something used by nvidia-current is accidentally uninitialized, but when there is no xorg.conf, xorg loads many other drivers (and then unloads all but the best choice during startup) and one of those other drivers happens to initialize that something. apt-cache policy nvidia-current nvidia-current: Installed: 280.13-0ubuntu6 Candidate: 280.13-0ubuntu6 Version table: *** 280.13-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ oneiric/restricted i386 Packages 100 / --- The attachment contains an xorg.conf created by nvidia-settings. When that (or ANY!) conf was in use, emacs triggered a segmentation violation, as shown in the file Xorg.0.log-SEGV. Looking at the file: Xorg.0.log, note that without being told what to do by an xorg.conf, Xorg loaded, in sequence, the six modules: [ 6529.541] (II) LoadModule: nvidia [ 6529.541] (II) LoadModule: nouveau [ 6529.542] (II) LoadModule: nv [ 6529.542] (II) LoadModule: vesa [ 6529.543] (II) LoadModule: fbdev [ 6529.545] (II) LoadModule: fbdevhw and then unloaded in sequence the five modules [ 6529.541] (II) LoadModule: nouveau [ 6529.542] (II) LoadModule: nv [ 6529.542] (II) LoadModule: vesa [ 6529.543] (II) LoadModule: fbdev [ 6529.545] (II) LoadModule: fbdevhw So that the only one of the original six that remained was nvidia. It seems a reasonable hypothesis that one of the other five modules performed an initialization that nvidia should have performed, but did not, and without that initialization having taken place in the instance of Xorg which had an xorg.conf, when emacs exercised a code path which involved the uninitialized item, the SEGV ensued. ** Affects: nvidia-graphics-drivers (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/930350 Title: xorg.conf plus emacs causes abrupt logout via Xorg SEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/930350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930350] Re: xorg.conf plus emacs causes abrupt logout via Xorg SEGV
** Attachment added: xorg.conf and 2 xorg logs https://bugs.launchpad.net/bugs/930350/+attachment/2730144/+files/Xorg-logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930350 Title: xorg.conf plus emacs causes abrupt logout via Xorg SEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/930350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
I had written: How do you get the workaround above to work when the host won't boot? Duh! I just had to scroll down to the generics that were just off screen, so now I can install the workaround. Selecting the package linux-virtual fortunately does not de-install linux-generic, but it does cause the host system's grub config to be updated to boot linux-virtual by default. Was the current linux-virtual released without first trying to boot a host system? If someone had tried a simple reboot after installing linux-virtual, they would have noticed that the host could no longer boot! Unless they had manually installed the workaround as well, simply knowing that it was needed rather than relying on the dependency mwechanism. Someone will probably respond that you are not supposed to install linux-virtual on a host machine. And it's probably even documented somewhere. But if that's the case, shouldn't there be some check performed to prevent (or at least warn about) it's installation on a host machine? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
Well I THOUGHT I was preparing to use virtualbox on oneiric when I apparently downloaded that virtual kernel. Now the system I was going to use as host is failing to boot with those ahci: unknown symbol messages, as well as getting HDIO_GET_IDENTITY failed for /dev/sda: Invalid Argument messages. How do you get the workaround above to work when the host won't boot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 923534] [NEW] problem with embedded mime types in linux firefox 9.0.1 on ubuntu oneiric
Public bug reported: Patent Images at the U.S. Patent office are loaded with code such as, for example,: embed src=/.DImg?Docid=06254230PageNum=1IDKey=A126567080D1 ImgFormat=tif width=570 height=840 type=image/tiff/embed xine-plugin is installed, but, A) when trying to access the patent images, one gets the message A plugin is required to display this content. B) opening a tiff file that has been manually downloaded (using a href=file:///pathname) brings up the desired image, but getting the image to that path is a hassle, especially when a patent has quite a few images, as one must view the source, grab the desired URL of each image that has failed to display, and fetch it manually to save it to a file, which can then be viewed using a hand crafted /a href=... . Using an image viewer manually saves that last step, but one must still initially view the source to get the URL, etc... ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: firefox 9.0.1+build1-0ubuntu0.11.10.2 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mab2567 F pulseaudio /dev/snd/controlC0: mab2567 F pulseaudio BuildID: 20111228084953 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC882' Components : 'HDA:10ec0882,104313c4,00100101 HDA:15433155,10431335,00100700' Controls : 36 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'Speaker'/'HOLTEK AudioHub Speaker at usb-:00:1d.7-2.4, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:0a0e' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 51 Mono: Playback 26 [51%] [-20.00dB] [on] Channel: release Date: Sun Jan 29 14:56:53 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) IpRoute: default via 192.168.0.1 dev wlan3 proto static 169.254.0.0/16 dev wlan3 scope link metric 1000 192.168.0.0/24 dev wlan3 proto kernel scope link src 192.168.0.29 metric 2 Profiles: Profile0 (Default) - LastVersion=9.0.1/20111228084953 (Running) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to oneiric on 2011-11-02 (88 days ago) WifiSyslog: Jan 29 10:07:30 ubuntu1 wpa_supplicant[1566]: WPA: Group rekeying completed with 00:24:a5:ad:79:54 [GTK=TKIP] Jan 29 14:15:45 ubuntu1 dhclient: DHCPREQUEST of 192.168.0.29 on wlan3 to 192.168.0.1 port 67 Jan 29 14:15:45 ubuntu1 dhclient: DHCPACK of 192.168.0.29 from 192.168.0.1 Jan 29 14:15:45 ubuntu1 dhclient: bound to 192.168.0.29 -- renewal in 35504 seconds. dmi.bios.date: 11/28/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G2S dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr212:bd11/28/2007:svnASUSTeKComputerInc.:pnG2S:pvr1.0:rvnASUSTeKComputerInc.:rnG2S:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: G2S dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/923534 Title: problem with embedded mime types in linux firefox 9.0.1 on ubuntu oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/923534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 923534] Re: problem with embedded mime types in linux firefox 9.0.1 on ubuntu oneiric
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/923534 Title: problem with embedded mime types in linux firefox 9.0.1 on ubuntu oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/923534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
