[Bug 1726548] Re: Windows resized after resume
I can confirm for Ubuntu 19.10 doing `gsettings set org.gnome.desktop.interface scaling-factor 1` has resolved my issue with Terminal windows on my Dell XPS13 set to 1920x1080 when the native LCD is capable of 3200x1800. I now have 100% scaling in the Display control panel thingie and my Terminal windows don't resize on their own after closing the lid and reopening. Thanks for the tip. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662137] Re: 16.04 recovery shell works only for two minutes
I have Bionic with friendly-recovery 0.2.38ubuntu1 and the problem still occurs. I apparently had three filesystems that were in "timeout". I went to recovery to see what was causing this and got ~120 seconds before the session was destroyed and the recovery options menu was redisplayed. I couldn't get anything to work after that. I hit down arrow many times to try to get to the root shell item and it moved down one line to the second menu item after a few down arrow keys and then wouldn't budge. To me it seems there are SEVERAL (at least two, but maybe more) shells all competing for keystrokes. FYI: I think the filesystem errors were caused by my installation of a new NVMe SSD and knocking loose a SATA interface cable or two. I think this is a good way to reproduce this problem, in fact. Set up several filesystems (EXT4 or BTRFS or even VFAT) on a drive then power off and pull the cable and boot again. You'll likely see the same effect I had. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662137 Title: 16.04 recovery shell works only for two minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1662137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567612] Re: postinst fails when settings in debian.cnf no longer work
I was able to conquer this problem by copying the /etc/mysql/debian.cnf-5.7 to /etc/mysql/debian.cnf and running sudo apt install -f one more time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567612 Title: postinst fails when settings in debian.cnf no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1567612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568224] Re: psmouse FingerSensingPad lost synchronization, throwing bytes away
I just booted today's Yakitty build on my machine and it still does it. I had to rmmod psmouse && modprobe psmouse so I could get the browser to work to post this. [ 80.835756] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 4 [ 80.836859] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 80.837960] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 80.839077] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 80.840168] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 80.840170] psmouse serio1: issuing reconnect request [ 81.613700] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 81.645671] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 217.321490] psmouse serio1: bad data from KBC - timeout [ 218.272129] psmouse serio1: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away. [ 218.808424] psmouse serio1: resync failed, issuing reconnect request [ 219.585201] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 219.616949] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 238.545960] psmouse serio1: bad data from KBC - timeout [ 239.509207] psmouse serio1: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away. [ 240.024227] psmouse serio1: resync failed, issuing reconnect request [ 240.800995] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 240.832990] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 243.921783] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 243.953564] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 291.111518] wlp4s0: authenticate with 14:cc:20:75:bc:6c [ 291.345834] wlp4s0: send auth to 14:cc:20:75:bc:6c (try 1/3) [ 291.347024] wlp4s0: authenticated [ 291.349107] wlp4s0: associate with 14:cc:20:75:bc:6c (try 1/3) [ 291.350565] wlp4s0: RX AssocResp from 14:cc:20:75:bc:6c (capab=0x11 status=0 aid=1) [ 291.351961] wlp4s0: associated [ 291.351993] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [ 1192.919946] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 4 [ 1210.862390] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 1210.892614] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 1210.954314] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [ 1210.954320] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [ 1210.993622] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568224 Title: psmouse FingerSensingPad lost synchronization, throwing bytes away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1568224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573300] Re: ssh -X X11 forwarding doesn't work
I can use one machine to start an X11 forwarded client on another. I did this to start gnome-terminal on a Ubuntu Server 16.04 from a Kubuntu 16.04 desktop by using ssh -Y -f 192.168.0.89 gnome-terminal This works. Then I look at that gnome-terminal's environment and DISPLAY and SSH_CLIENT variables are properly set: DISPLAY=localhost:10.0 SSH_CLIENT=192.168.0.215 38634 22 Then I look for listeners on TCP port #6010 as is implied by the above DISPLAY envar: $ netstat -anl4 Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 127.0.0.1:250.0.0.0:* LISTEN tcp0 0 192.168.0.84:22 192.168.0.215:38542 ESTABLISHED tcp0 0 192.168.0.84:22 192.168.0.215:36110 ESTABLISHED udp0 0 0.0.0.0:68 0.0.0.0:* No such listener. I did this same sort of ssh connection from my desktop Kubuntu to a Raspberry Pi running Raspbian and the rpi has a listener as I would expect it to. I believe this lack of a listener for the ssh on the remote machine to allow X11 clients to connect back to the server through "screen :10" is what is missing. In in /etc/ssh/sshd_config on the target Ubuntu 16.04 server machine I have this for X11 forwarding configuration: $ cat /etc/ssh/sshd_config | grep -i x11 X11Forwarding yes X11DisplayOffset 10 I have always been able to get this to work with previous Ubuntu releases (14.04, the 15.x series, etc.). This is something specific to changes in Xenial. It looks like the release notes (https://launchpad.net/ubuntu/xenial/+source/openssh/+changelog) include some changes for this area of ssh. Maybe the fix for this (http://www.openssh.com/txt/x11fwd.adv) partially borked ssh's X11 forwarding mechanism? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573300 Title: ssh -X X11 forwarding doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1573300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573300] Re: ssh -X X11 forwarding doesn't work
I just re-read the originator report for this bug. My problem is not exactly the same as his in that I DO get a X11 forwarded client to work but I cannot connect any more of them except through additional X11 forwarded ssh commands from the original client. Should I report this as a separate bug? I think it might be distinct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573300 Title: ssh -X X11 forwarding doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1573300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450806] [NEW] virtualbox-dkms 4.3.10-dfsg-1ubuntu4: virtualbox kernel module failed to build
Public bug reported: I have a Linus tree kernel v3.19.2 built using Ubuntu config + defaults for new options. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-dkms 4.3.10-dfsg-1ubuntu4 Uname: Linux 3.19.2 x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 DKMSKernelVersion: 3.19.2 Date: Fri May 1 07:26:52 2015 DuplicateSignature: dkms:virtualbox-dkms:4.3.10-dfsg-1ubuntu4:/var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c:186:48: error: macro alloc_netdev requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-09-26 (217 days ago) InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all PackageVersion: 4.3.10-dfsg-1ubuntu4 SourcePackage: virtualbox Title: virtualbox-dkms 4.3.10-dfsg-1ubuntu4: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450806 Title: virtualbox-dkms 4.3.10-dfsg-1ubuntu4: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1450806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348430] Re: btrfs send does not work for snapshots in subvolumes
I had this problem as well, and my situation was a little more complicated to use the workaround. My subvolume that was being snapshotted for 'btrfs send' to use was at the top of the hierarchy - there WAS no parent. But BTRFS always has a parent, so there is still a workaround. My situation: root@diskybiz:~# btrfs subv list /x ID 258 gen 13525 top level 5 path home ID 259 gen 13521 top level 5 path backups ID 553 gen 1724 top level 5 path home/@snap-20140811-082041 ID 621 gen 13524 top level 5 path home/backup001 As you can see, the very top of the hierarchy is ID 258 or /home. I wanted to use that snapshot at ID 621 for my 'btrfs send' command. I had to determine the parent of the ID 258 subvolume, which I did by btrfs subv show /home and looking at the Parent: line. This happens to be the same as the top level number shown in teh btrfs subv list, but I wasn't sure that was a subvolume ID, so I went this extra step. Then I just mounted another mountpoint for my BTRFS filesystem like this: root@diskybiz:~# mount -o subvolid=5 /dev/sdc1 /x That made the root of the filesystem visible on /x. Then I could do my 'btrfs send' like so: root@diskybiz:~# btrfs send /x/ /root/home-backup-20141001.btrfs I hope this helps someone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348430 Title: btrfs send does not work for snapshots in subvolumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1348430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367455] [NEW] MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison
Public bug reported:
The comparison used in provisioningserver/utils/__init__.py:
find_ip_via_arp(mac) compares MAC addresses to the output of an arp -n
command using case sensitive comparison. This MAC address may be entered
by a user in a web UI and often is NOT cut/pasted from ARP but rather
from the IPMI vendor's display, which may display the MAC address in
uppercase.
For a fix, I strongly recommend doing these things to make this more
friendly:
1. Trim all whitespace from the supplied MAC address before comparison.
2. Trim all delimiters too - both on the supplied MAC address and from
the output column of the arp -n it's being compared with.
3. Translate both the supplied MAC address and the arp -n column data
to lowercase or uppercase for comparison or use a case-insensitive match
in the for loop.
- DIFF -
diff /usr/lib/python2.7/dist-packages/provisioningserver/utils/__init__.py
__init__.py
46a47
import re
824a826,827
mac = mac.lower()
mac = re.sub('[^0-9a-f]', '', mac)
829c832,833
if len(columns) == 5 and columns[2] == mac:
---
col = re.sub('[^0-9a-f]', '', columns[2])
if len(columns) == 5 and col == mac:
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1367455
Title:
MAC address for node's IPMI is reversed looked up to yield IP address
using case sensitive comparison
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1367455/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367455] Re: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison
OK the diff was useless, and I'm sorry. But I'm not a python weenie, nor do I do diffs everyday for bug reports. The code, which is trivial to someone who writes python all the time, is easy in any case. Thank you for playing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1367455 Title: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1367455/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367455] Re: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison
Oh and the proposed code has a bug too - don't look at columns[2] without checking for len(columns) == 5. Sheesh. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1367455 Title: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1367455/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367455] [NEW] MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison
Public bug reported:
The comparison used in provisioningserver/utils/__init__.py:
find_ip_via_arp(mac) compares MAC addresses to the output of an arp -n
command using case sensitive comparison. This MAC address may be entered
by a user in a web UI and often is NOT cut/pasted from ARP but rather
from the IPMI vendor's display, which may display the MAC address in
uppercase.
For a fix, I strongly recommend doing these things to make this more
friendly:
1. Trim all whitespace from the supplied MAC address before comparison.
2. Trim all delimiters too - both on the supplied MAC address and from
the output column of the arp -n it's being compared with.
3. Translate both the supplied MAC address and the arp -n column data
to lowercase or uppercase for comparison or use a case-insensitive match
in the for loop.
- DIFF -
diff /usr/lib/python2.7/dist-packages/provisioningserver/utils/__init__.py
__init__.py
46a47
import re
824a826,827
mac = mac.lower()
mac = re.sub('[^0-9a-f]', '', mac)
829c832,833
if len(columns) == 5 and columns[2] == mac:
---
col = re.sub('[^0-9a-f]', '', columns[2])
if len(columns) == 5 and col == mac:
** Affects: maas (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/1367455
Title:
MAC address for node's IPMI is reversed looked up to yield IP address
using case sensitive comparison
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1367455/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367455] Re: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison
Oh and the proposed code has a bug too - don't look at columns[2] without checking for len(columns) == 5. Sheesh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367455 Title: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1367455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367455] Re: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison
OK the diff was useless, and I'm sorry. But I'm not a python weenie, nor do I do diffs everyday for bug reports. The code, which is trivial to someone who writes python all the time, is easy in any case. Thank you for playing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367455 Title: MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1367455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1334143] Re: Sorry, I can't find the 'mpost' preload file; will try 'plain'.
I think you need to install 'texlive-metapost' and maybe even 'texlive- full' to get the necessary files. This should be more obvious. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1334143 Title: Sorry, I can't find the 'mpost' preload file; will try 'plain'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1334143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300087] Re: Error in `/usr/share/doc-base/gcc-4.8-itm', line 29: format `html' already defined
This is caused by the file /usr/share/doc-base/gcc-4.8-itm having two complete copies of its normal content. If I delete the file and then install gcc-4.8-doc, both copies are put into the file and the installation effectively fails to install properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300087 Title: Error in `/usr/share/doc-base/gcc-4.8-itm', line 29: format `html' already defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doc-base/+bug/1300087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074748] [NEW] ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
Public bug reported: Sorry if this is repeat. I have no log saying WHY the bug occurred. But it is probably included in the secret developer info :) ProblemType: Package DistroRelease: Ubuntu 12.10 Package: ndiswrapper-dkms ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DKMSKernelVersion: 3.5.0-17-generic Date: Sat Nov 3 14:20:10 2012 InstallationDate: Installed on 2011-05-05 (548 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.57-1ubuntu1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build UpgradeStatus: Upgraded to quantal on 2012-11-03 (0 days ago) ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074748 Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1074748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007011] [NEW] package libjline-java 1.0-1 failed to install/upgrade: trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400
Public bug reported: Sorry I know nothing more to say about this. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libjline-java 1.0-1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Fri May 25 12:21:14 2012 Dependencies: DpkgTerminalLog: Unpacking libjline-java (from .../libjline-java_1.0-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/libjline-java_1.0-1_all.deb (--unpack): trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400 DuplicateSignature: Unpacking libjline-java (from .../libjline-java_1.0-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/libjline-java_1.0-1_all.deb (--unpack): trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400 ErrorMessage: trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) PackageArchitecture: all SourcePackage: jline Title: package libjline-java 1.0-1 failed to install/upgrade: trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400 UpgradeStatus: Upgraded to precise on 2012-05-17 (13 days ago) ** Affects: jline (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007011 Title: package libjline-java 1.0-1 failed to install/upgrade: trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jline/+bug/1007011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007011] Re: package libjline-java 1.0-1 failed to install/upgrade: trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007011 Title: package libjline-java 1.0-1 failed to install/upgrade: trying to overwrite '/usr/share/java/jline.jar', which is also in package scala 2.9.2-400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jline/+bug/1007011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 877699] Re: sky2 ethernet broken in 3.0.0-12.20 x86_64
I have sporadic driver failure with the 3.0.0-12 released kernel. I upgraded to the 3.0.7-030007-generic driver and found that the failure still occurs. It's sporadic - within a day. It is barely possible that the failure is less likely with the newer driver, but I don't think I have enough data yet to be statistically valid in that statement. Unless the originator's problem is different from mine (mine works at first then fails), it's still borked in 3.0.7. More info: The failure results in the device being permanently wedged for transmit only. I can and do still receive packets. But tx always results in no output onto the wire (not even with a bad CRC). Unloading and reloading the driver doesn't fix this. Only a reboot (and, I suspect, the associated hardware reset) fixes it. Driver output from dmesg: [1.810972] sky2: driver version 1.28 [1.811008] sky2 :04:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.811019] sky2 :04:00.0: setting latency timer to 64 [1.811044] sky2 :04:00.0: Yukon-2 EC Ultra chip revision 2 [1.811138] sky2 :04:00.0: irq 44 for MSI/MSI-X Below is what looks like it is the output from the hang event when I was running 3.0.0-12-generic kernel. Interesting that the rx path is the one on the stack when the failure occurs. Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846739] eth0: hw csum failure. Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846746] Pid: 0, comm: swapper Tainted: P C 3.0.0-12-generic #20-Ubuntu Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846748] Call Trace: Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846750] IRQ [814d60c2] netdev_rx_csum_fault+0x42/0x50 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846762] [814ce940] __skb_checksum_complete_head+0x60/0x70 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846766] [814ce961] __skb_checksum_complete+0x11/0x20 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846770] [815554e7] nf_ip_checksum+0x57/0x100 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846781] [a0ca291c] tcp_error+0xfc/0x280 [nf_conntrack] Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846788] [a0c9eb0f] nf_conntrack_in+0xef/0x540 [nf_conntrack] Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846792] [8152ed91] ? tcp_v4_do_rcv+0xb1/0x200 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846797] [a0cb7f31] ipv4_conntrack_in+0x21/0x30 [nf_conntrack_ipv4] Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846802] [81504c45] nf_iterate+0x85/0xc0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846805] [8150c100] ? inet_del_protocol+0x40/0x40 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846808] [81504cf6] nf_hook_slow+0x76/0x130 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846811] [8150c100] ? inet_del_protocol+0x40/0x40 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846815] [8150cacd] ip_rcv+0x20d/0x2f0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846819] [815a5587] ? packet_rcv_spkt+0x47/0x190 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846823] [814d8222] __netif_receive_skb+0x4a2/0x540 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846826] [814d8de0] netif_receive_skb+0x80/0x90 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846829] [814d91d8] ? dev_gro_receive+0x1b8/0x2c0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846832] [814d8f20] napi_skb_finish+0x50/0x70 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846835] [814d9455] napi_gro_receive+0xb5/0xc0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846847] [a0027743] sky2_status_intr+0x363/0x430 [sky2] Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846853] [a002788a] sky2_poll+0x7a/0x150 [sky2] Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846856] [814d9664] net_rx_action+0x134/0x290 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846861] [a002583a] ? sky2_intr+0x5a/0x60 [sky2] Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846866] [81065f58] __do_softirq+0xa8/0x210 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846870] [8108d205] ? do_timer+0x25/0x30 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846875] [815e9efe] ? _raw_spin_lock+0xe/0x20 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846878] [815f34dc] call_softirq+0x1c/0x30 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846882] [8100c2d5] do_softirq+0x65/0xa0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846885] [8106633e] irq_exit+0x8e/0xb0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846888] [815f3d33] do_IRQ+0x63/0xe0 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846891] [815ea413] common_interrupt+0x13/0x13 Nov 17 11:24:39 alan-desk-ubuntu kernel: [16932.846893] EOI [81012457] ? mwait_idle+0x87/0x160 Nov 17 11:24:39 alan-desk-ubuntu kernel:
[Bug 616102] [NEW] Description says STM32 Primer2 platform is supported, but it isn't
Public bug reported: Binary package hint: openocd Description for this package says STM32 Primer2 platform is supported. I don't believe it can be supported. According to OpenOCD's documentation PDF: 2.5 USB RLINK based Raisonance has an adapter called RLink. It exists in a stripped-down form on the STM32 Primer, permanently attached to the JTAG lines. It also exists on the STM32 Primer2, but that is wired for SWD and not JTAG, thus not supported. Furthermore, now that I have bought this platform on the basis of this description, I find that it doesn't work :(. Prove me wrong and I will buy you beer(s). ** Affects: openocd (Ubuntu) Importance: Undecided Status: New -- Description says STM32 Primer2 platform is supported, but it isn't https://bugs.launchpad.net/bugs/616102 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
