[Touch-packages] [Bug 1943964] Re: local var="$@" doesn't behave like every other system
I thought I'd illustrate the problem. Given a #!/bin/sh script like this called tst: #!/bin/sh f() { local v="$@" echo "<$V>" } f "$@" On Debian, Fedora, FreeBSD, OpenBSD, macOS, and Solaris, the arguably incorrect but more useful behaviour is: > ./tst a b c > ./tst 1 2 3 <1 2 3> On Ubuntu, the arguably correct but less useful behaviour is: > ./tst a b c > ./tst 1 2 3 ./tst: 4: local: 2: bad variable name On NetBSD, the behaviour is very similar to Ubuntu's, but not identical: > ./tst a b c > ./tst 1 2 3 local: 2: bad variable name <1> It seems that "bad variable name" is a fatal error on Ubuntu, but not on NetBSD. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1943964 Title: local var="$@" doesn't behave like every other system Status in dash package in Ubuntu: New Bug description: With Ubuntu (for many years), the following code in /bin/sh (i.e. dash): f() { local v="$@" echo "<$v>" } f "$@" behaves differently to /bin/sh on Debian, macOS, FreeBSD, Solaris (/usr/xpg4/bin/sh). The behaviour of "$@" is very special. When there are no arguments, it completely disappears (i.e. even the surrounding quotes disappear so that there are no words). When there are arguments, it replicates those arguments perfectly (i.e. it effectively produces multiple quoted arguments if necessary). The described behaviour applies when "$@" is used for local variable assignment on Ubuntu, which sounds consistent with other uses of "$@" and therefore correct, but it doesn't match the behaviour on any other system, and is therefore a problem for shell portability. On the other systems mentioned above, the behaviour of "$@" when used as the value of a variable assignment (local or not) is as though "$*" had been used (i.e. it produces a single argument containing all the words). The difference is clear when the arguments contain multiple words. On Ubuntu, only the first word is assigned to v. Any subsequent words are treated as subsequent variable names. This goes unnoticed if the subsequent words are valid variable identifiers. But if the subsequent words are not valid identifiers, then dash emits a "bad variable name" error message. Note that without the "local" keyword, "$@" does behave like "$*" (like all the other systems). You might think that this is correct behaviour, but it is contrary to non-local variable assignment, and contrary to all other systems, and is therefore unhelpful. Please change it to behave like dash on other systems, e.g. debian. This behaviour has been witnessed on ubuntu-16.x and ubuntu-20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1943964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943964] [NEW] local var="$@" doesn't behave like every other system
Public bug reported: With Ubuntu (for many years), the following code in /bin/sh (i.e. dash): f() { local v="$@" echo "<$v>" } f "$@" behaves differently to /bin/sh on Debian, macOS, FreeBSD, Solaris (/usr/xpg4/bin/sh). The behaviour of "$@" is very special. When there are no arguments, it completely disappears (i.e. even the surrounding quotes disappear so that there are no words). When there are arguments, it replicates those arguments perfectly (i.e. it effectively produces multiple quoted arguments if necessary). The described behaviour applies when "$@" is used for local variable assignment on Ubuntu, which sounds consistent with other uses of "$@" and therefore correct, but it doesn't match the behaviour on any other system, and is therefore a problem for shell portability. On the other systems mentioned above, the behaviour of "$@" when used as the value of a variable assignment (local or not) is as though "$*" had been used (i.e. it produces a single argument containing all the words). The difference is clear when the arguments contain multiple words. On Ubuntu, only the first word is assigned to v. Any subsequent words are treated as subsequent variable names. This goes unnoticed if the subsequent words are valid variable identifiers. But if the subsequent words are not valid identifiers, then dash emits a "bad variable name" error message. Note that without the "local" keyword, "$@" does behave like "$*" (like all the other systems). You might think that this is correct behaviour, but it is contrary to non-local variable assignment, and contrary to all other systems, and is therefore unhelpful. Please change it to behave like dash on other systems, e.g. debian. This behaviour has been witnessed on ubuntu-16.x and ubuntu-20.04. ** Affects: dash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1943964 Title: local var="$@" doesn't behave like every other system Status in dash package in Ubuntu: New Bug description: With Ubuntu (for many years), the following code in /bin/sh (i.e. dash): f() { local v="$@" echo "<$v>" } f "$@" behaves differently to /bin/sh on Debian, macOS, FreeBSD, Solaris (/usr/xpg4/bin/sh). The behaviour of "$@" is very special. When there are no arguments, it completely disappears (i.e. even the surrounding quotes disappear so that there are no words). When there are arguments, it replicates those arguments perfectly (i.e. it effectively produces multiple quoted arguments if necessary). The described behaviour applies when "$@" is used for local variable assignment on Ubuntu, which sounds consistent with other uses of "$@" and therefore correct, but it doesn't match the behaviour on any other system, and is therefore a problem for shell portability. On the other systems mentioned above, the behaviour of "$@" when used as the value of a variable assignment (local or not) is as though "$*" had been used (i.e. it produces a single argument containing all the words). The difference is clear when the arguments contain multiple words. On Ubuntu, only the first word is assigned to v. Any subsequent words are treated as subsequent variable names. This goes unnoticed if the subsequent words are valid variable identifiers. But if the subsequent words are not valid identifiers, then dash emits a "bad variable name" error message. Note that without the "local" keyword, "$@" does behave like "$*" (like all the other systems). You might think that this is correct behaviour, but it is contrary to non-local variable assignment, and contrary to all other systems, and is therefore unhelpful. Please change it to behave like dash on other systems, e.g. debian. This behaviour has been witnessed on ubuntu-16.x and ubuntu-20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1943964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu
Sorry, previous post was UNRELATED to the bug, I changed the swap partition location and my PC (strangely after to perfect reboots) started looking for it elsewhere... The .deb file has worked fine for me as well! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1542743 Title: Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu Status in bluez package in Ubuntu: Confirmed Bug description: Since some Versions of Linux Kernel and Ubuntu Releases this problem exists. I am now running ubuntu 16.04 prerelease and still have the same problem. Bluetooth does not work with the atheros device on msi gt 72 2qd notebook. WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4: sudo apt install dkms wget https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files /btusb-lp1542743-dkms_0.2~4.8_all.deb dmesg | grep Bluetooth: [2.655360] Bluetooth: Core ver 2.21 [2.655373] Bluetooth: HCI device and connection manager initialized [2.655377] Bluetooth: HCI socket layer initialized [2.655379] Bluetooth: L2CAP socket layer initialized [2.655385] Bluetooth: SCO socket layer initialized [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.612794] Bluetooth: BNEP filters: protocol multicast [6.612798] Bluetooth: BNEP socket layer initialized [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu [9.016882] Bluetooth: Loading patch file failed hwinfo | grep Bluetooth: <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 <6>[6.612794] Bluetooth: BNEP filters: protocol multicast <6>[6.612798] Bluetooth: BNEP socket layer initialized <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu <3>[9.016882] Bluetooth: Loading patch file failed 60: USB 00.0: 11500 Bluetooth Device Model: "Atheros AR3012 Bluetooth 4.0" Device: usb 0x3004 "AR3012 Bluetooth 4.0" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.36-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Sun Feb 7 00:38:04 2016 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-10-24 (105 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: bnep btusb bluetooth MachineType: Micro-Star International Co., Ltd. GT72 2QD ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10I dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QD dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu
Hi there, I've installed the latest patch given because I was suffering from the same bluetooth issue. Unfortunately after the patch my boot sequence has become excruciatingly long!!! this is where it stops for ~2 minutes: [CODE] May 10 09:55:58 Aaron-Linux systemd[1]: Started Tell Plymouth To Write Out Runtime Data. May 10 09:55:58 Aaron-Linux systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:1d.0/:3c:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 and /sys/devices/pci:00/:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sda/sda4 May 10 09:55:58 Aaron-Linux systemd[1]: Found device Crucial_CT1050MX300SSD1 HAL. May 10 09:55:58 Aaron-Linux apparmor[665]: * Starting AppArmor profiles May 10 09:55:58 Aaron-Linux systemd[1]: Mounting /mnt/HAL... May 10 09:55:58 Aaron-Linux systemd[1]: Activating swap Swap Partition... May 10 09:55:58 Aaron-Linux systemd[1]: Starting Network Time Synchronization... May 10 09:55:58 Aaron-Linux systemd[1]: Starting Update UTMP about System Boot/Shutdown... May 10 09:55:58 Aaron-Linux apparmor[665]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 10 09:55:58 Aaron-Linux systemd[1]: Activated swap Swap Partition. May 10 09:55:58 Aaron-Linux systemd[1]: Started Set console font and keymap. May 10 09:55:58 Aaron-Linux apparmor[665]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 10 09:55:58 Aaron-Linux systemd-timesyncd[760]: The system is configured to read the RTC time in the local time zone. This mode can not be fully supported. All system time to RTC updates are disabled. May 10 09:55:58 Aaron-Linux systemd[1]: Started Network Time Synchronization. May 10 09:55:58 Aaron-Linux systemd[1]: Reached target System Time Synchronized. May 10 09:55:58 Aaron-Linux systemd[1]: Created slice system-getty.slice. May 10 09:55:58 Aaron-Linux systemd[1]: Started Update UTMP about System Boot/Shutdown. May 10 09:55:58 Aaron-Linux apparmor[665]:...done. May 10 09:55:58 Aaron-Linux systemd[1]: Started LSB: AppArmor initialization. May 10 09:55:58 Aaron-Linux systemd[1]: Starting Raise network interfaces... May 10 09:55:58 Aaron-Linux systemd[1]: Started Raise network interfaces. May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Version 2015.3.14AR.1 integrated FUSE 28 May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Mounted /dev/sda4 (Read-Write, label "HAL", NTFS 3.1) May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Cmdline options: rw,nosuid,nodev May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,fsname=/dev/sda4,blkdev,blksize=4096 May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Ownership and permissions disabled, configuration type 7 May 10 09:55:58 Aaron-Linux systemd[1]: Mounted /mnt/HAL. May 10 09:55:58 Aaron-Linux mtp-probe: checking bus 1, device 5: "/sys/devices/pci:00/:00:14.0/usb1/1-11" May 10 09:55:58 Aaron-Linux mtp-probe: checking bus 1, device 2: "/sys/devices/pci:00/:00:14.0/usb1/1-1" May 10 09:55:58 Aaron-Linux mtp-probe: checking bus 1, device 3: "/sys/devices/pci:00/:00:14.0/usb1/1-3" May 10 09:55:58 Aaron-Linux mtp-probe: bus: 1, device: 2 was not an MTP device May 10 09:55:58 Aaron-Linux mtp-probe: bus: 1, device: 5 was not an MTP device May 10 09:55:58 Aaron-Linux mtp-probe: bus: 1, device: 3 was not an MTP device May 10 09:55:58 Aaron-Linux systemd[1]: Starting Load/Save RF Kill Switch Status... May 10 09:55:58 Aaron-Linux systemd[1]: Started Load/Save RF Kill Switch Status. May 10 09:55:58 Aaron-Linux systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... May 10 09:55:58 Aaron-Linux systemd[1]: Started Braille Device Support. May 10 09:55:58 Aaron-Linux systemd[1]: Started Tell Plymouth To Write Out Runtime Data. May 10 09:55:58 Aaron-Linux systemd[1]: dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device: Job dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device/start timed out. [\CODE] Furthermore while the laptop is sitting on my desk it keeps logging out this crap: [CODE] May 10 09:56:54 Aaron-Linux os-prober: debug: /dev/sda5: is active swap May 10 09:56:57 Aaron-Linux gnome-session[1462]: (gnome-shell:1652): St-WARNING **: Ignoring excess values in shadow definition May 10 09:56:57 Aaron-Linux gnome-session[1462]: message repeated 7 times: [ (gnome-shell:1652): St-WARNING **: Ignoring excess values in shadow definition] May 10 09:57:01 Aaron-Linux google-chrome.desktop[6995]: [1,1449989952:07:57:01.033389] Native Client module will be loaded at base address 0x095b May 10 09:57:19 Aaron-Linux systemd[1]: dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device: Job dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device/start timed out. May 10 09:57:19 Aaron-Linux systemd[1