[Touch-packages] [Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec

2022-05-18 Thread wdoekes
Ahyes, that fixes things on Ubuntu/Jammy as well: mkdir -p /etc/apparmor.d/disable # (did not exist, over here) ln -s /etc/apparmor.d/usr.bin.tcpdump /etc/apparmor.d/disable # (note, no sbin, but bin) apparmor_parser -R /etc/apparmor.d # (this is indeed needed, instead of an apparmor restart) -

[Touch-packages] [Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

2021-07-09 Thread wdoekes
How about this case: - I make a hypothetical package that depends on libxxhash < 0.8 because I want the "broken/old" xxh128 support; - I have libxxhash 0.7.3 (that came with Focal); - I have rsync 3.1.x (that came with Focal); - Now I release-upgrade my system from Focal to Groovy; - I get all

[Touch-packages] [Bug 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

2021-07-09 Thread wdoekes
Hi Wayne! Thanks for commenting. > It's only the 128-bit hash that depends on 0.8.0. > The 0.7 version works fine with rsync, giving it > the 64-bit and 32-bit hashes. Yes. Except it seems that if you switch the libxxhash0 from 0.8 to 0.7, you get different behaviour. rsync doesn't check what ki

[Touch-packages] [Bug 1934992] [NEW] rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

2021-07-08 Thread wdoekes
Public bug reported: **Problem** $ rsync root@focal-system:/etc/.pwd.lock . ERROR: .pwd.lock failed verification -- update discarded. rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1816) [generator=3.2.3] $ rsync root@focal-system:/etc/

[Touch-packages] [Bug 1350782] Re: Upstart does not reopen /var/log/upstart/* logfiles upon log rotation

2017-03-28 Thread wdoekes
A google search turned up this as the most likely candidate for my logrotate+gzip issues. I'm going to try this for a workaround: /var/log/upstart/*.log { daily missingok rotate 7 compress notifempty nocreate # Added by wjd 2017-03 for launchpad b

[Touch-packages] [Bug 1465959] Re: In phones with two SIMs, if you don't unlock SIM1, the message for unlocking SIM2 says "SIM1"

2016-01-14 Thread wdoekes
I think so. I did a single attempt at reproducing it recently, I didn't succeed. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1465959 Title: In phones

[Touch-packages] [Bug 1426307] Re: location is inaccurate

2015-09-02 Thread wdoekes
I've never had GPS location work without the HERE functions enabled. As soon as I disable it (I have to restart for a change to take effect) I get *no* location info whatsoever. (I have waited for weeks to get a GPS lock, to no avail.) The SensorsStatus tool tells me (when HERE is enabled) that I

[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch

2015-08-17 Thread wdoekes
Same here. I had the "Using GPS only" since I bought the phone and GPS never worked. Days/weeks of uptime should be enough to get a GPS lock, right? Now I enabled the GPS/Wifi/mobile-network ("HERE"), rebooted, and like you said, within 30 seconds, the SensorsStatus tool started reporting GPS info

[Touch-packages] [Bug 1447502] Re: "GPS/location" icon in notification top bar is out of sync with settings

2015-05-22 Thread wdoekes
No idea; I only noticed this when initially using the phone. If you think it's fixed in the next version, I'll believe you. I'll reopen if it happens again. Thanks! ** Changed in: indicator-location (Ubuntu) Status: New => Fix Released ** Changed in: indicator-location (Ubuntu RTM)

[Touch-packages] [Bug 1447479] Re: SIM Pin1 and Pin2 headings get mixed up sometimes

2015-05-19 Thread wdoekes
100% reproducible: - boot with dual sim, - when it says sim 1: press X (to cancel) - then it says sim 1, but it wants sim 2 code - enter sim 2 code - at this point, only sim 2 is activated, - authenticate, go to network, unlock sim 1, now it says "sim 2" but wants sim 1 code -- You received thi

[Touch-packages] [Bug 1452161] Re: Leaving flight mode, unlocking on dual SIM: header PIN's title prompt does not match with the SIM's number

2015-05-19 Thread wdoekes
*** This bug is a duplicate of bug 1447479 *** https://bugs.launchpad.net/bugs/1447479 ** This bug has been marked a duplicate of bug 1447479 SIM Pin1 and Pin2 headings get mixed up sometimes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, w

[Touch-packages] [Bug 1447502] [NEW] "GPS/location" icon in notification top bar is out of sync with settings

2015-04-23 Thread wdoekes
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: - even though I've disabled GPS and "Location detection", the crosshair icon is always on. - after playing around with *enabling* the GPS and waiting a bit, the ico

[Touch-packages] [Bug 1447499] [NEW] "Rotation locked" icon in notification top bar icon is counter intuitive

2015-04-23 Thread wdoekes
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: - the "Rotation locked" icon appears as "phone which can be rotated", which is illogical to me. If the rotation is locked, then I'd expect the icon to cross out the

[Touch-packages] [Bug 1447482] Re: Notification area is readable/editable while in screen-lock mode

2015-04-23 Thread wdoekes
*** This bug is a duplicate of bug 1358340 *** https://bugs.launchpad.net/bugs/1358340 Oops. Hadn't found those. Sorry. Disabling both the "Launcher" and "Notifications and quick settings" suits my needs. Thanks! -- You received this bug notification because you are a member of Ubuntu Touc

[Touch-packages] [Bug 1447482] [NEW] Notification area is readable/editable while in screen-lock mode

2015-04-23 Thread wdoekes
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: even though the phone is supposed to be locked, one can: - read incoming messages from the notification (top swipe) area, - change on/off state of bluetooth, gps, wi

[Touch-packages] [Bug 1447479] [NEW] SIM Pin1 and Pin2 headings get mixed up sometimes

2015-04-23 Thread wdoekes
Public bug reported: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've had the following issue: - both SIMs are inserted, I'm asked to unlock one SIM, and the text above says SIM2 while in fact it wanted the pin code for SIM1 (and vice versa): notably, the co

[Touch-packages] [Bug 1387207] Re: [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter

2015-04-23 Thread wdoekes
** Summary changed: - [greeter] strange persistant "Enter SIM1 PIN" dialog on Greeter + [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in

[Touch-packages] [Bug 1031718] Re: Obscure error messages caused by ubuntu patch

2014-10-23 Thread wdoekes
So. Apparently this has been "fixed" somewhere along the road to Ubuntu 14.04. The patch is commented out in the debian/patches/series file in version 1.3.0-0ubuntu2. However, the debian/changelog doesn't tell me when that happened (or when it was added, for that matter). -- You received this

[Touch-packages] [Bug 406397] Re: init: job stuck with expect fork/daemon when parent reaps child

2014-08-25 Thread wdoekes
And I'm happy to say that things are moving to systemd. My cron.conf now looks #44 just so cron gets the right locale in 14.04. I'm baffled that that's the best I can come up with with upstart. If there is a better way, please enlighten me. -- You received this bug notification because you are a

[Touch-packages] [Bug 406397] Re: init: job stuck with expect fork/daemon when parent reaps child

2014-08-25 Thread wdoekes
Nice tip MarcS. That is indeed better than the other workarounds. Here, a quick script -- cleanup-upstart.sh -- that checks initctl list for stalled processes and kills them: #!/bin/sh # vim: set ts=8 sw=4 sts=4 et ai tw=71: upstart_spawn_and_stop() { name=$1 pid=$2 pkill -xf 'slee

[Touch-packages] [Bug 1322843] Re: foregrounding a sudo'd vim will sometimes break terminal state

2014-08-25 Thread wdoekes
That last patch is the sudo author's fix for the issue. Bug is still open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1322843 Title: foregrounding a sudo'd vim will somet

[Touch-packages] [Bug 1322843] Re: foregrounding a sudo'd vim will sometimes break terminal state

2014-08-25 Thread wdoekes
** Patch added: "SUDO-649_Patch-to-ignore-program-generated-SIGTSTP--si_pid.patch" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1322843/+attachment/4186391/+files/SUDO-649_Patch-to-ignore-program-generated-SIGTSTP--si_pid.patch -- You received this bug notification because you are a m