[Bug 1733011] Re: smbd crash after reboot
** Attachment added: "log.nmbd" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+attachment/5101248/+files/log.nmbd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733011 Title: smbd crash after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733011] Re: smbd crash after reboot
** Attachment added: "log.smbd" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+attachment/5101249/+files/log.smbd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733011 Title: smbd crash after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733011] Re: smbd crash after reboot
Took a while before the server was rebooted. Attached log.nmbd, log.smbd and smbd.conf ** Attachment added: "smb.conf" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+attachment/5101247/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733011 Title: smbd crash after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606472] Re: boot scripts hang in plymouth --ping (aka: Plymouth's bug returns)
I get the same problem on a fairly fresh 17.10 desktop installation on a Lenovo P51 laptop. Whenever I install a new kernel, the dkms installation calls plymouth --ping which hangs forever. It seems killing plymouth in these cases will progress the build, but it has to be done multiple times per dkms run. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606472 Title: boot scripts hang in plymouth --ping (aka: Plymouth's bug returns) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1606472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733011] Re: smbd crash after reboot
Sure, but do you need *everything* from /var/log/samba/log* ? This is running on a production server, and I've got 63 files in this directory. I need to wash them to ensure I don't publish any sensitive data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733011 Title: smbd crash after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1733011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733011] [NEW] smbd crash after reboot
Public bug reported: Running Ubuntu 16.04.3 LTS, with samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 My problem is that smbd stops after reboot. If I manually restart the smbd service, the service starts normally. # systemctl status smbd ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled) Active: active (exited) since Fri 2017-11-17 21:57:16 CET; 1h 41min ago Docs: man:systemd-sysv-generator(8) Process: 2250 ExecStart=/etc/init.d/smbd start (code=exited, status=0/SUCCESS) Tasks: 0 Memory: 0B CPU: 0 Nov 17 21:57:12 neo systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)... Nov 17 21:57:15 neo smbd[2250]: * Starting SMB/CIFS daemon smbd Nov 17 21:57:16 neo smbd[2250]:...done. Nov 17 21:57:16 neo systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd). /var/log/samba/log.smbd reveals that smbd has crashed [2017/11/17 21:57:15.984660, 0] ../source3/lib/interface.c:543(load_interfaces) WARNING: no network interfaces found [2017/11/17 21:57:16.209233, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connections [2017/11/17 21:57:16.209963, 0] ../source3/smbd/server.c:877(open_sockets_smbd) open_sockets_smbd: No sockets available to bind to. [2017/11/17 21:57:16.210191, 0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 2263): open_sockets_smbd() failed [2017/11/17 21:57:16.210643, 0] ../source3/lib/util.c:900(log_stack_trace) BACKTRACE: 9 stack frames: #0 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(log_stack_trace+0x1a) [0x7fc5520257aa] #1 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(smb_panic_s3+0x20) [0x7fc552025880] #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fc552d98f1f] #3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x144461) [0x7fc552998461] #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1447a1) [0x7fc5529987a1] #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-shim.so.0(exit_server+0x12) [0x7fc550872c52] #6 /usr/sbin/smbd(main+0x131e) [0x557e93538b1e] #7 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fc54f555830] #8 /usr/sbin/smbd(_start+0x29) [0x557e93539199] [2017/11/17 21:57:16.210797, 0] ../source3/lib/util.c:801(smb_panic_s3) smb_panic(): calling panic action [/usr/share/samba/panic-action 2263] [2017/11/17 21:57:16.212999, 0] ../source3/lib/util.c:809(smb_panic_s3) smb_panic(): action returned status 0 [2017/11/17 21:57:16.213070, 0] ../source3/lib/dumpcore.c:303(dump_core) dumping core in /var/log/samba/cores/smbd (no core dump can be found at the indicated location unfortunately.) With some aid in #ubuntu-server, this can probably be related to the sequencing of network coming up. This server use DHCP assigned server addresses, so there will be a delay between ifup and network being online. As can be seen below: smbd seems to be starting much earlier than network online, while nmbd is started after network online. Nov 17 21:57:11 neo kernel: r8169 :03:00.0 enp3s0: link up Nov 17 21:57:11 neo kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready Nov 17 21:57:12 neo dhclient[2055]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0x376d3044) Nov 17 21:57:12 neo sh[2019]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0x376d3044) Nov 17 21:57:12 neo dhclient[2055]: DHCPREQUEST of 10.5.5.10 on enp3s0 to 255.255.255.255 port 67 (xid=0x44306d37) Nov 17 21:57:12 neo sh[2019]: DHCPREQUEST of 10.5.5.10 on enp3s0 to 255.255.255.255 port 67 (xid=0x44306d37) Nov 17 21:57:12 neo sh[2019]: DHCPOFFER of 10.5.5.10 from 10.5.5.1 Nov 17 21:57:12 neo dhclient[2055]: DHCPOFFER of 10.5.5.10 from 10.5.5.1 Nov 17 21:57:12 neo dhclient[2055]: DHCPACK of 10.5.5.10 from 10.5.5.1 Nov 17 21:57:12 neo sh[2019]: DHCPACK of 10.5.5.10 from 10.5.5.1 Nov 17 21:57:12 neo systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)... Nov 17 21:57:15 neo smbd[2250]: * Starting SMB/CIFS daemon smbd Nov 17 21:57:16 neo smbd[2250]:...done. Nov 17 21:57:16 neo systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd). Nov 17 21:57:17 neo dhclient[2055]: bound to 10.5.5.10 -- renewal in 33991 seconds. Nov 17 21:57:17 neo sh[2019]: bound to 10.5.5.10 -- renewal in 33991 seconds. Nov 17 21:57:18 neo systemd[1]: Started Raise network interfaces. Nov 17 21:57:18 neo systemd[1]: Reached target Network. Nov 17 21:57:18 neo systemd[1]: Starting A high performance web server and a reverse proxy server... Nov 17 21:57:18 neo systemd[1]: Starting Statistics collection and monitoring daemon... Nov 17 21:57:18 neo systemd[1]: Starting OpenBSD Secure Shell server... Nov 17 21:57:18 neo systemd[1]: Starting Docker Application Container Engine... Nov 17 21:57:18 neo systemd[1]: Started Unattended Upgrades Shutdown. Nov 17 21:57:18 neo systemd[1]: Reached target Network is Online. Nov 17
[Bug 860432] Re: tried to grab repository for wrong architecture
I confirm the bug. I didn't find this bug using multistrap, I rather used a custom script of my own which is attached here. It's purpose is to download a armel package and all its dependencies. This script works when being run on a Natty amd64 and i386 host machine, while it fails on Precise amd64: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/natty/main/binary-i386/Packages 404 Not Found W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/natty/universe/binary-i386/Packages 404 Not Found W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/natty-updates/main/binary-i386/Packages 404 Not Found W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/natty-updates/universe/binary-i386/Packages 404 Not Found W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/natty-security/main/binary-i386/Packages 404 Not Found W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/natty-security/universe/binary-i386/Packages 404 Not Found ** Attachment added: Tool to recreate bug https://bugs.launchpad.net/ubuntu/+source/multistrap/+bug/860432/+attachment/3189400/+files/apt-wrap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/860432 Title: tried to grab repository for wrong architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/860432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 860432] Re: tried to grab repository for wrong architecture
Both approaches have been tested and confirmed. I'm going to stick with setting the APT::Architectures as I have less control of the real sources.list 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/860432 Title: tried to grab repository for wrong architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/860432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947988] [NEW] fixrtc kernel option always sets system time
Public bug reported: On Natty armel, the kernel option 'fixrtc' exists to set the system time from the last mount time from the rootfs. This allows systems which does not have a valid RTC time at startup to be able to boot of the root file system. When the 'fixrtc' option is used, the system time is set to the last mount time, regardless if the system time is already set to something valid. There should be a comparison between the current system time and the last mount time. The fixrtc should only come into play if the system time is less than the last mount time of the fs. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: armel natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947988 Title: fixrtc kernel option always sets system time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/947988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886690] [NEW] qemu segfaults in armel chroot on i386 host
Public bug reported: Running on i386 on Natty. Using qemu-user-static 0.14.50-2011.03-1-0ubuntu2. Bug occurs only on i386 Natty. amd64 Natty does not show described behaviour, neither does Oneiric i386. The attached script creates an armel chroot directory using qemu- debootstrap and then tries to install 'openssh-server' inside the chroot (by implicitly using the binfmt emulation). If the script is invoked directly: sudo ./qemufail.sh it does not fail. If the script is invoked indirectly via make it fails: sudo make qemufail with a Makefile containing qemufail: \n ./qemufail.sh, it returns: Setting up openssh-server (1:5.8p1-1ubuntu3) ... Creating SSH2 RSA key; this may take some time ...qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: qemu-user-static 0.14.50-2011.03-1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Sat Nov 5 23:06:17 2011 Dependencies: InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu-linaro UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qemu-linaro (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886690 Title: qemu segfaults in armel chroot on i386 host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/886690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886690] Re: qemu segfaults in armel chroot on i386 host
** Attachment added: Script to provoke bug https://bugs.launchpad.net/bugs/886690/+attachment/2586671/+files/qemufail.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886690 Title: qemu segfaults in armel chroot on i386 host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/886690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787831] Re: Meld crashes if svn working dir contains svn externals dirs
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787831 Title: Meld crashes if svn working dir contains svn externals dirs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/787831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770549] Re: meld /path/to/folder doesn't work
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770549 Title: meld /path/to/folder doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/meld/+bug/770549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 786134] Re: Meld chokes on file comparison
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/786134 Title: Meld chokes on file comparison To manage notifications about this bug go to: https://bugs.launchpad.net/meld/+bug/786134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774265] Re: [natty] meld hangs comparing attached files
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774265 Title: [natty] meld hangs comparing attached files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/774265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886690] Re: qemu segfaults in armel chroot on i386 Natty host
** Summary changed: - qemu segfaults in armel chroot on i386 host + qemu segfaults in armel chroot on i386 Natty host -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886690 Title: qemu segfaults in armel chroot on i386 Natty host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/886690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886690] Re: qemu segfaults in armel chroot on i386 Natty host
Using the Linaro Tools PPA for Natty ( https://launchpad.net/~linaro- maintainers/+archive/tools/?field.series_filter=natty ) version 0.15.50-2011.10-0ubuntu1~ppa11.04.1 of qemu-user-static, qemu doesn't segfault. I.e. the script works when called directly and via make. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886690 Title: qemu segfaults in armel chroot on i386 Natty host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/886690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798095] [NEW] upowerd grabs my FTDI USB serial port adapter
Public bug reported: Binary package hint: upower Running on natty on amd64. upower 0.9.9-4. I have a development board with a build-in generic FTDI USB Serial port adapter (USB VID:PID 0403:6001). When I plug this into my computer, upowerd grabs (opens) the serialport and thus prevent me from using the serial port. ** Affects: upower (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/798095 Title: upowerd grabs my FTDI USB serial port adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/798095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798095] Re: upowerd grabs my FTDI USB serial port adapter
This bug is due to a udev rule in /lib/udev/rules.d/95-upower-wup.rules. This udev rule erroneously assumes that USB VID:PID 0403:6001 is assigned to Watts Up? Pro from Watts Up Inc. The VID:PID is rather assiged to a FT232 USB Serial adapter chip from FTDI Inc. The FT232 is a generic electronic part which is default configured with the said VID and PID. This part is used in a lot of development boards and different kind of products. It cannot be assumed that this VID and PID belongs to the Watts Up Pro product. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798095 Title: upowerd grabs my FTDI USB serial port adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/798095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787831] [NEW] Meld crashes if svn working dir contains svn externals dirs
Public bug reported: Binary package hint: meld If I run meld in a SVN working copy to display local modifications, meld crashes if the working copy contains a SVN externals directory. The following traceback is given: Traceback (most recent call last): File /usr/lib/meld/meld/task.py, line 130, in iteration ret = task() File /usr/lib/meld/meld/vcview.py, line 330, in _search_recursively_iter entries = filter(showable, self.vc.listdir(root)) File /usr/lib/meld/meld/vc/_vc.py, line 166, in listdir dirs, files = self.lookup_files(cdirs, cfiles) File /usr/lib/meld/meld/vc/_vc.py, line 175, in lookup_files return self._get_dirsandfiles(directory, dirs, files) File /usr/lib/meld/meld/vc/svn.py, line 105, in _get_dirsandfiles for match in self._get_matches(directory): File /usr/lib/meld/meld/vc/svn.py, line 95, in _get_matches rev = status.attrib[revision] KeyError: 'revision' System info: Natty on amd64. meld 1.5.0-0ubuntu1 ** Affects: meld (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/787831 Title: Meld crashes if svn working dir contains svn externals dirs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 761645] Re: Custom icon does not appear in launcher
Same here. I created a new launcher with a custom icon on the desktop to firefox -chat to directly start chatzilla. When the launcher is moved to the unity launcher the custom icon is discarded and unity is instead using the firefox icon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/761645 Title: Custom icon does not appear in launcher -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683832] Re: gcc fails to cross compile Qt
This is a confirmed bug in Qt and not in gcc. Using -marm fixes the issue. ** Changed in: gcc-4.5-armel-cross (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683832 Title: gcc fails to cross compile Qt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683832] Re: gcc fails to cross compile Qt
This is a confirmed bug in Qt and not in gcc. Using -marm fixes the issue. ** Changed in: gcc-4.4-armel-cross (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683832 Title: gcc fails to cross compile Qt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692987] Re: [armel-cross] this linker was not configured to use sysroots
As a temporary workaround, you can pin the binutils-arm-linux-gnueabi to version 2.20.51.20100908-0ubuntu2cross1.50. It seems to still linger around the various Ubuntu mirrors. Please note the sysroot setting was removed from binutils due to bug #598389, so don't expect xdeb to work properly with the pinned binutils version. I'm currently considering repackaging the binutils package with sysroot enabled for those of us which needs it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692987 Title: [armel-cross] this linker was not configured to use sysroots -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692987] Re: [armel-cross] this linker was not configured to use sysroots
Its a pity that sysroot support is disabled and will not be enabled. In fact this is a major and serious obstacle for our company and puts spokes in the wheels for an upcoming software release. Now we need to find or configure an alternate toolchain. The beauty of Ubuntu's armel-cross was that is was configured with libc friends equal to the native armel target, making it a decent cross compiler for an Ubuntu target environment. To use the cross compiler in this manner, you'd need the support from sysroot to properly build and link applications (outside of xdeb) which won't get confused when running on target. So, if the sysroot setting is gone for good, then I'm very sorry, because this was something we really needed. Are there any commercial parties tied up to Canonical etc. which can make a toolchain with sysroot enabled on request? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692987 Title: [armel-cross] this linker was not configured to use sysroots -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683832] [NEW] gcc fails to cross compile Qt
Public bug reported:
Building fails when cross compiling building embedded Qt (not for X11). After a
little while the compilation stops with the message:
{standard input}: Assembler messages:
{standard input}:26712: Error: selected processor does not support Thumb mode
`swp r3,r2,[r1]'
The error occurs on arm-linux-gnueabi-gcc version 4.5.1 and 4.5.1. The
error does not, however, occur on the Code Sourcery G++ Lite compiler
(version 2010q1-202 - gcc 4.4.1)
Host system is Maverick, amd64. The bug has been confimed on g++-4.4
-arm-linux-gnueabi version 4.4.4-14ubuntu4 and on g++-4.5-arm-linux-
gnueabi version 4.5.1-7ubuntu1cross1.38
Steps to reproduce the bug:
*) Please note the attached patch is for configuring Qt to use the
Ubuntu armel-cross compiler instead of using the code sourcery compiler.
$ git clone git://gitorious.org/qt/qt.git -b 4.7-stable
Topmost commit is currently: caca740ea1219227008c303b5f2fac24af5a62a0
$ cd qt
$ git apply ../ubuntu-gnueabi.diff
$ cd ..
$ mkdir qt-build
$ cd qt-build
$ ../qt/configure \
-opensource \
-confirm-license \
-hostprefix `pwd`/qt-bin \
-prefix /opt/qt \
-fast \
-embedded arm \
-little-endian \
-platform linux-g++ \
-xplatform qws/linux-arm-gnueabi-g++ \
-arch arm \
-no-openssl \
-no-cups \
-no-largefile \
-no-qt3support \
-no-webkit \
-no-libmng \
-no-libjpeg \
-no-libtiff \
-no-gif \
-no-script \
-no-scripttools \
-no-sql-sqlite \
-no-accessibility \
-no-multimedia \
-no-nis \
-qt-mouse-pc \
-plugin-mouse-pc \
-exceptions \
-xmlpatterns \
-nomake demos \
-nomake examples \
-nomake docs \
-nomake translations \
-D QT_NO_QWS_CURSOR \
-D QT_QWS_CLIENTBLIT
$ make
...
arm-linux-gnueabi-g++ -c -include .pch/release-shared-emb-arm/QtCore -pipe
-march=armv7-a -mtune=cortex-a8 -mfloat-abi=softfp -mfpu=neon
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC
-DQT_SHARED -DQT_NO_QWS_CURSOR -DQT_QWS_CLIENTBLIT -DQT_BUILD_CORE_LIB
-DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS
-DQT_MOC_COMPAT -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION
-DELF_INTERPRETER=\/lib64/ld-linux-x86-64.so.2\ -DHB_EXPORT=Q_CORE_EXPORT
-DQT_NO_DEBUG -I/home/user/temp/gcc-bug/qt/mkspecs/qws/linux-arm-gnueabi-g++
-I/home/user/temp/gcc-bug/qt/src/corelib -I../../include -I../../include/QtCore
-I.rcc/release-shared-emb-arm -Iglobal
-I/home/user/temp/gcc-bug/qt/src/3rdparty/zlib
-I/home/user/temp/gcc-bug/qt/src/3rdparty/harfbuzz/src
-I/home/user/temp/gcc-bug/qt/src/3rdparty/md5
-I/home/user/temp/gcc-bug/qt/src/3rdparty/md4 -I.moc/release-shared-emb-arm -I.
-o .obj/release-shared-emb-arm/qobject.o
/home/user/temp/gcc-bug/qt/src/corelib/kernel/qobject.cpp
{standard input}: Assembler messages:
{standard input}:26712: Error: selected processor does not support Thumb mode
`swp r3,r2,[r1]'
make[1]: *** [.obj/release-shared-emb-arm/qobject.o] Error 1
make[1]: Leaving directory `/home/user/temp/gcc-bug/qt-build/src/corelib'
make: *** [sub-corelib-make_default-ordered] Error 2
** Affects: gcc-4.4-armel-cross (Ubuntu)
Importance: Undecided
Status: New
--
gcc fails to cross compile Qt
https://bugs.launchpad.net/bugs/683832
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 683832] Re: gcc fails to cross compile Qt
** Patch added: Patch to Qt to use the armel-cross compiler https://bugs.launchpad.net/bugs/683832/+attachment/1751888/+files/ubuntu-gnueabi.diff -- gcc fails to cross compile Qt https://bugs.launchpad.net/bugs/683832 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 683839] [NEW] gcc fails to cross compile Qt
Public bug reported: See bug #683832 in gcc-4.4-armel-cross for description ** Affects: gcc-4.5-armel-cross (Ubuntu) Importance: Undecided Status: New -- gcc fails to cross compile Qt https://bugs.launchpad.net/bugs/683839 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 452350] Re: Unknown LVM metadata header
I have a fresh installation of Lucid with manually modified lvm2 partitions. I have /dev/sda1 as ext2 /boot partition, while /dev/sda5 is a PV for the LVM2. I got the same header checksum error from all lvm2 tools and update-grub. Doing a pvscan revealed that /dev/sda1 is an available PV member of the LVM, when it's only used as a standard partition for /boot. I don't know if that's good or bad, but Mike's solution worked. However I had to do some extra steps on a running system: - umount /dev/sda1 - pvremove /dev/sda1 - blkid /dev/sda1 and then replace the UUID into /etc/fstab where /dev/sda1 is mounted (/boot) - mount /dev/sda1 -- Unknown LVM metadata header https://bugs.launchpad.net/bugs/452350 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 556482] [NEW] kernel crash when booting on AM3517-EVM
Public bug reported: Failed to boot lucid on a AM3517-EVM due to kernel crash. Kernel output is attached. Target system is TI AM3517-EVM (Cortex A8). System is ubuntu-minimal lucid built from rootstock, using kernel linux-image-2.6.33-500-omap (2.6.33-500.4) ** Affects: linux-ti-omap (Ubuntu) Importance: Undecided Status: New ** Tags: armel -- kernel crash when booting on AM3517-EVM https://bugs.launchpad.net/bugs/556482 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 556482] Re: kernel crash when booting on AM3517-EVM
** Attachment added: ti-omap-kernel-output.txt http://launchpadlibrarian.net/43244225/ti-omap-kernel-output.txt -- kernel crash when booting on AM3517-EVM https://bugs.launchpad.net/bugs/556482 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 548353] [NEW] ssh to localhost fails in qemu for lucid image
Public bug reported: Binary package hint: rootstock Running Ubuntu Karmic x64 host. Using a patched version (version 31) of the karmic rootstock script. Create the lucid image: $ sudo ./rootstock --fqdn ssh-test --login demo --password demo --imagesize 1G --seed ubuntu-minimal,openssh-server --dist lucid --notarball and start qemu with $ qemu-system-arm -M versatilepb -cpu cortex-a8 -kernel vmlinuz -hda qemu-armel-201003252208.img -m 256 -append root=/dev/sda mem=256M devtmpfs.mount=0 rw The command ssh d...@localhost will prompt a RSA fingerprint warning and the password query. When the password has been entered, the login locks up. The lockup is not limited to localhost. The same lockup applies if a ssh session is tried connected from any internal or external network source on all network devices, like the host tun/tap interface. tcpdump reveals that the guest receives the messages from the ssh client, but does not reply to them. ** Affects: rootstock (Ubuntu) Importance: Undecided Status: New -- ssh to localhost fails in qemu for lucid image https://bugs.launchpad.net/bugs/548353 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
