[Bug 1470019] Re: light-locker-command -a crashes

2016-09-22 Thread MikeyB
I feel it's important to note that it's not just 'light-lock-command -a'
that fails, but any attempt to lock the screen fails, such as the
display timeout.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470019

Title:
  light-locker-command -a crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1470019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1470019] Re: light-locker-command -a crashes

2016-09-22 Thread MikeyB
+1: can we please flag this as a security issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470019

Title:
  light-locker-command -a crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1470019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1470019] Re: light-locker-command -a crashes

2016-09-09 Thread MikeyB
This affects the LTS as well:

```
michael@kronos:~
○ → lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

michael@kronos:~
○ → light-locker-command -a

(light-locker-command:14886): GLib-CRITICAL **: the GVariant format
string '(b)' has a type of '(b)' but the given value has a type of '(s)'

(light-locker-command:14886): GLib-CRITICAL **: g_variant_get: assertion 
'valid_format_string (format_string, TRUE, value)' failed
```

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470019

Title:
  light-locker-command -a crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1470019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1390623] Re: VPN with IPv6 connectivity but no IPv6 DNS server results in broken DNS config

2015-08-25 Thread MikeyB
Affects 15.04 as well.

before VPN:
Aug 25 21:20:14 challenger dnsmasq[2049]: setting upstream servers from DBus
Aug 25 21:20:14 challenger dnsmasq[2049]: using nameserver 2001:db8:b0e2::51#53
Aug 25 21:20:14 challenger dnsmasq[2049]: using nameserver 2001:db8:b0e2::52#53
Aug 25 21:20:14 challenger dnsmasq[2049]: using nameserver 192.168.1.51#53
Aug 25 21:20:14 challenger dnsmasq[2049]: using nameserver 192.168.1.52#53

after VPN:
Aug 25 21:20:20 challenger dnsmasq[2049]: using nameserver 192.168.0.6#53 for 
domain netdirect.ca
Aug 25 21:20:20 challenger dnsmasq[2049]: using nameserver 192.168.0.6#53 for 
domain 31.172.in-addr.arpa
Aug 25 21:20:20 challenger dnsmasq[2049]: using nameserver 192.168.0.6#53 for 
domain 10.in-addr.arpa
Aug 25 21:20:20 challenger dnsmasq[2049]: using nameserver 192.168.0.6#53 for 
domain 0.168.192.in-addr.arpa
Aug 25 21:20:20 challenger dnsmasq[2049]: using nameserver 192.168.0.6#53 for 
domain 235.16.216.in-addr.arpa

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390623

Title:
  VPN with IPv6 connectivity but no IPv6 DNS server results in broken
  DNS config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot

2014-10-18 Thread MikeyB
Is there any way to mark this as affecting the 14.04 LTS? It's status
fix-released, but the fix has *not* actually been released.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273201

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot

2014-10-15 Thread MikeyB
I see the fix released for 14.10, ETA for this to be backported to
trusty?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273201

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot

2014-09-07 Thread MikeyB
Looks like this also affects my configuration:
http://askubuntu.com/q/520051/9083

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273201

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1326810] [NEW] ping forgets to whom it's talking

2014-06-05 Thread MikeyB
Public bug reported:

Distro: ubuntu 14.04 x64
Package: iputils-ping 3:20121221-4ubuntu1.1

The ping command accidentally uses the information for the last ICMP
UNREACHABLE response instead of the host from which the *actual*
response came. See the output below:

michael@challenger:~
○ → ping 10gb-sw1
PING 10gb-sw1.office.netdirect.ca (192.168.0.33) 56(84) bytes of data.
>From challenger.netdirect.ca (192.168.0.135) icmp_seq=1 Destination Host 
>Unreachable
>From challenger.netdirect.ca (192.168.0.135) icmp_seq=2 Destination Host 
>Unreachable
…
>From challenger.netdirect.ca (192.168.0.135) icmp_seq=82 Destination Host 
>Unreachable
>From challenger.netdirect.ca (192.168.0.135) icmp_seq=86 Destination Host 
>Unreachable
64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=88 ttl=255 
time=3.25 ms
64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=89 ttl=255 
time=0.737 ms
64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=90 ttl=255 
time=1.68 ms
…
64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=96 ttl=255 
time=2.83 ms
^C
--- 10gb-sw1.office.netdirect.ca ping statistics ---
96 packets transmitted, 9 received, +56 errors, 90% packet loss, time 95015ms
rtt min/avg/max/mdev = 0.737/2.427/3.966/1.156 ms, pipe 4

michael@challenger:~
○ → ping 10gb-sw1
PING 10gb-sw1.office.netdirect.ca (192.168.0.33) 56(84) bytes of data.
64 bytes from 10gb-sw1.netdirect.ca (192.168.0.33): icmp_seq=1 ttl=255 
time=4.34 ms
64 bytes from 10gb-sw1.netdirect.ca (192.168.0.33): icmp_seq=2 ttl=255 
time=2.97 ms
64 bytes from 10gb-sw1.netdirect.ca (192.168.0.33): icmp_seq=3 ttl=255 
time=2.14 ms
^C
--- 10gb-sw1.office.netdirect.ca ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 2.146/3.156/4.344/0.907 ms

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: iputils-ping 3:20121221-4ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun  5 09:50:13 2014
InstallationDate: Installed on 2013-09-09 (268 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
SourcePackage: iputils
UpgradeStatus: Upgraded to trusty on 2014-04-18 (48 days ago)

** Affects: iputils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326810

Title:
  ping forgets to whom it's talking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1326810/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1058407] Re: --preserve-data dysfunctional

2013-11-20 Thread MikeyB
Specifically, add the following check:

if not self.preserve_dest_disks:
raise RuntimeError(
_("Clone onto existing storage volume is not "
  "currently supported: '%s'") % clone_disk.path)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058407

Title:
  --preserve-data dysfunctional

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/1058407/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 775950] Re: fixing recursive fault but reboot is needed! upon boot (always reproducible on battery only, but sometimes on AC too)

2013-08-10 Thread MikeyB
This is affecting me on a fresh install on a TravelMate 5520.

The live CD works fine, but attempting to boot to the installed OS leads
to the 'fixing recursive fault but reboot is needed' error during the
boot sequence.

No combination of 'noapic', 'xforcevesa', 'acpi=off', 'nomodeset'
helped.

I tried fresh installs of 12.04.02 and 13.04, with no luck.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/775950

Title:
  fixing recursive fault but reboot is needed! upon boot (always
  reproducible on battery only, but sometimes on AC too)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775950/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 960820] Re: xserver-xorg-input-joystick not behaving

2012-07-06 Thread MikeyB
Do note that this bug still affects 12.04 LTS. I tested on my system as
well as someone else's (fresher) 12.04 install.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960820

Title:
  xserver-xorg-input-joystick not behaving

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-joystick/+bug/960820/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 960820] [NEW] xserver-xorg-input-joystick not behaving

2012-03-20 Thread MikeyB
Public bug reported:

Ubuntu 11.04, xserver-xorg-input-joystick version 1.5.99+git20101214
.8c7ad54d-0ubuntu3

I've configured my X-Box gamepad for use as an X cursor as follows:

# Left stick
Option "MapAxis1" "mode=relative axis=+1x  deadzone=3000"
Option "MapAxis2" "mode=relative axis=+1y  deadzone=3000"
# Right stick
Option "MapAxis4" "mode=relative axis=+1zx deadzone=3000"
Option "MapAxis5" "mode=relative axis=+1zy deadzone=3000"
# Left trigger
Option "MapAxis3" "mode=none"
# Right trigger
Option "MapAxis6" "mode=none"
# D-pad
Option "MapAxis7" "mode=accelerated axis=+0.5x  deadzone=2000"
Option "MapAxis8" "mode=accelerated axis=+0.5y  deadzone=2000"

# A button
Option "MapButton1" "button=2"
# B button
Option "MapButton2" "button=3"
# X button
Option "MapButton3" "button=1"
# Y button
Option "MapButton4" "button=2"
# X-Box button
Option "MapButton9" "disable-mouse"
# Rest of the buttons
Option "MapButton5" "none"
Option "MapButton6" "none"
Option "MapButton7" "none"
Option "MapButton8" "none"
Option "MapButton10" "none"
Option "MapButton11" "none"

Everything's working as configured except for a critical problem:
When Axis 1 crosses into positive values (right), the cursor is immediately 
moved all the way to the left of the screen (and keeps getting pushed that way 
until Axis 1 crosses back into negative (left). Note that this does not respect 
the dead zone.

When Axis 2 crosses into positive values (down), the cursor is
immediately moved all the way to the top of the screen (and keeps
getting pushed that way until Axis 2 crosses back into negative (down).
Note that this does not respect the dead zone.

(the same thing happens with the zx/zy axes, so you get the idea)

** Affects: xserver-xorg-input-joystick (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/960820

Title:
  xserver-xorg-input-joystick not behaving

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-joystick/+bug/960820/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 53927] Re: Please include queuefreeze patch in future kernel builds

2006-07-24 Thread MikeyB


-- 
Please include queuefreeze patch in future kernel builds
https://launchpad.net/bugs/53927

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 53927] Please include queuefreeze patch in future kernel builds

2006-07-24 Thread MikeyB
Public bug reported:

Binary package hint: linux-image-2.6.15-26-686

The distro kernels include hdaps support (thank you!) however we cannot
freeze hard drives when a shock is detected.

Please add the queuefreeze patch to the kernel builds - note that it
does not (fingers crossed :) affect people who do not choose to use it.

I've worked the patch to apply cleanly against 2.6.15 sources - see:
http://www.supermathie.net/~michael/linux-source-2.6.15-mikeyb-queuefreeze.patch

** Affects: linux-source-2.6.15 (Ubuntu)
 Importance: Untriaged
 Status: Unconfirmed

-- 
Please include queuefreeze patch in future kernel builds
https://launchpad.net/bugs/53927

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs