[Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

2018-05-06 Thread Max Bowsher
** Also affects: linux (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/1765911

Title:
  Major performance regression from Ubuntu 17.10 with i915

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

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

[Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

2018-05-05 Thread Max Bowsher
Similar/same issue observed on HP Spectre 13 (2017 model) which has
exactly the same Intel HD 520 graphics. Bad enough that I had to
reinstall 17.10.

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

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

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

[Bug 1762261] [NEW] Bug in Ubuntu patch for synaptics support prevents me configuring my touchpad same as previous Ubuntu releases

2018-04-08 Thread Max Bowsher
Public bug reported:

Touchpad handling appears to have been refactored somewhat in bionic -
which led to the surprise of having my settings changed on upgrade 
but even when I tracked down the new gsettings property of
org.gnome.desktop.peripherals.touchpad click-method, it fails to behave
as documented, so I cannot get the behaviour I want, and had before.

The code in function meta_input_settings_x11_set_click_method_synaptics
added by the patch interprets click-method 'default' as setting specific
settings.

However, the gsettings schema description says 'default' should mean
"left as hardware default".

Please change the patch to follow that, and not change the settings at
all - as having a way to tell mutter to get out of the way and let the
user configure their own settings is more useful than insisting on
applying a given hardcoded choice.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.0-2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr  8 23:49:12 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-16 (600 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: mutter
UpgradeStatus: Upgraded to bionic on 2018-04-04 (3 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Bug in Ubuntu patch for synaptics support prevents me configuring my
  touchpad same as previous Ubuntu releases

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

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

[Bug 1704799] Re: iwlwifi: 8260: missing iwlwifi-8000C-{22..30}.ucode firmware

2018-01-26 Thread Max Bowsher
It is expected that the -22.ucode file is missing because it was
deliberately removed per https://lists.ubuntu.com/archives/kernel-
team/2017-July/085667.html

The -27.ucode file was added in linux-firmware 1.165 and updated in
1.168

None of the other versions were ever released by Intel according to the
table at
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release

Thus, there doesn't actually appear to be any outstanding problem
tracked in this bug, so I'll set it to Fix Released.

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  iwlwifi: 8260: missing iwlwifi-8000C-{22..30}.ucode firmware

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2018-01-26 Thread Max Bowsher
Adding linux-firmware as an affected package - on further investigation,
it turns out that the real problem here appears to be firmware
incompatibility between the Wifi and Bluetooth parts of the 8260
package.

Relevant bug in Kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=197807

Relevant commit delivering updated firmware to upstream linux-
firmware.git repository fixing the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit?id=fdee922a785212be7ccced6809b337290fdac971

Ideally that would be SRUed into artful.

** Bug watch added: Linux Kernel Bug Tracker #197807
   https://bugzilla.kernel.org/show_bug.cgi?id=197807

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2018-01-26 Thread Max Bowsher
** Also affects: linux-firmware (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/1719210

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2018-01-15 Thread Max Bowsher
The exact manifestation of this seems to have changed (now the gnome
settings UI claims that my hardware doesn't have bluetooth support at
all - despite CLI bluetoothctl still being aware of it) but the basic
issue still very much remains: 4.13 from artful => bluetooth inoperable;
4.10 from zesty => works fine.

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1722109] Re: iwlwifi regression in artful - intermittent total packet loss

2017-10-10 Thread Max Bowsher
It is not possible to test the latest upstream kernel. It appears to
introduce further problems apparently related to apparmor which prevent
dhclient running, preventing a wifi connection from being successful at
all, as well as apparently causing display flickering, which is barely
perceptible at first glance, but stressful to observe whilst attempting
any substantial computer use.

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

Title:
  iwlwifi regression in artful - intermittent total packet loss

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

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

[Bug 1722109] Re: iwlwifi regression in artful - intermittent total packet loss

2017-10-10 Thread Max Bowsher
Unfortunately as the issue is intermittent, it is difficult to pinpoint
a starting version exactly, but here's my best attempt:

Ubuntu zesty 4.10 series: definitely not affected

Ubuntu artful 4.12 kernels: problem not observed, though other iwlwifi
issues (bug 1719210) observed - probably not affected

Ubuntu artful 4.13 kernels: 4.13.0-12.13 (current) definitely affected,
unable to conclusively comment if earlier artful versions affected or
not, due to already swapping kernels around a lot at the time
troubleshooting the other mentioned bug.


It's worth noting that there is a large change in the versions of the Intel 
iwlwifi firmware microcode loaded to the device between these mentioned kernel 
versions. Regrettably newer versions of the kernel have dropped support 
entirely for interacting with the known good microcode version, so it isn't 
possible to test changing the kernel and microcode versions independently.

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

Title:
  iwlwifi regression in artful - intermittent total packet loss

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

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

[Bug 1722109] [NEW] iwlwifi regression in artful - intermittent total packet loss

2017-10-08 Thread Max Bowsher
Public bug reported:

Recently I have been experiencing intermitted total packet loss over
wifi.

I've already been looking at another issue in which Bluetooth
coexistence seems to be causing controller hardware to crash - bug
1719210 - so I'm rather suspicious of the updated iwlwifi microcode that
is used by newer kernel versions.

Unfortunately, I don't have a good reproduction recipe, as the fault
doesn't seem to occur immediately after boot, nor is it an absolute
failure of connectivity - from a user perspective, it feels like, for
example, the website you are using is responding exceptionally slowly.
It is only on testing multiple remote sites, and finding that rebooting
into an earlier kernel fixes the issue, that it is apparent that it's a
local OS problem.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  maxb   1859 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  8 19:10:31 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
InstallationDate: Installed on 2016-08-16 (418 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Spectre Notebook
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-08-31 (37 days ago)
dmi.bios.date: 02/21/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81A0
dmi.board.vendor: HP
dmi.board.version: 48.54
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug artful

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

Title:
  iwlwifi regression in artful - intermittent total packet loss

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-10-08 Thread Max Bowsher
I also seem to now be having Bluetooth-unrelated issues with iwlwifi,
filed in bug 1722109

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-10-08 Thread Max Bowsher
Confirming this is very much *not* fixed - the last linux-firmware
upload doesn't seem to have touched anything iwlwifi-related at all:
https://launchpadlibrarian.net/339888041/linux-
firmware_1.168_1.169.diff.gz

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-10-04 Thread Max Bowsher
OK, I think I finally found the real trigger, helped by John Tanner's
comment and Googling the bt_coex_active option. It's trying to
simultaneously use bluetooth and a *2.4GHz* wifi network.

Trying that on my hardware results in lots of iwlwifi kernel logging
reporting that the device microcode keeps crashing and requiring a
hardware reset.

This happens both on 4.12 and 4.13, but 4.12 doesn't let it disrupt the
bluetooth audio stream, so I didn't notice, but 4.13 kills the bluetooth
connection.

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-10-04 Thread Max Bowsher
Or so I thought :-(I got set up for bisecting again, and now I can't
reproduce the problem at all.

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-10-04 Thread Max Bowsher
Hmm... empirically, I seem to have discovered a factor related to why
this sometimes works and sometimes does not with 4.13 - for me, the bug
only occurs if my laptop is booted *without* AC power applied.

Which makes no sense. But seems to be happening anyway.

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-09-28 Thread Max Bowsher
I am seriously confused.

As requested, I tested out a 4.14-rc - actually, I tested -rc2 since
that had come out - and the problem was present - audio playback would
freeze after around 40-50 seconds.

Then I went back to various 4.13 versions and attempted to get the start
of a bisection going - but I've been *unable to reproduce* the problem
with the same 4.13 versions that I initially filed the bug about.

It seems that I'm going to have to run 4.13 for a while, and try to
figure out a reliable reproduction recipe.

Yet, despite that, it seems that something is further wrong in 4.14
since it's reliably breaking there :-/

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-09-24 Thread Max Bowsher
Mainline ppa 4.12.14 is working OK

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-09-24 Thread Max Bowsher
Lack of functionality also a problem in mainline-ppa 4.13.3 version. The
following messages are logged to the journal:

Sep 24 21:44:05 spectre bluetoothd[826]: Unable to get Headset Voice gateway 
SDP record: Connection timed out
Sep 24 21:44:46 spectre bluetoothd[826]: connect error: Connection refused (111)

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1719210] [NEW] Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-09-24 Thread Max Bowsher
Public bug reported:

Using artful kernel 4.12.0-13.14, Bluetooth audio works great.

Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
audio issues which have manifested in a variety of weird ways:

1) Playback would stall after 10-20 seconds
2) Upon removing the device and attempting to redo pairing, no devices could be 
found to pair with
3) After the device ended up reverting to low quality mono HSP mode, it could 
not be switched back to A2DP

This is all rather vague - sorry - but it felt better to get notice of
this regression into the bugtracker sooner rather than later.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-11-generic 4.13.0-11.12
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  maxb   2091 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 24 21:24:00 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
InstallationDate: Installed on 2016-08-16 (404 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Spectre Notebook
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-11-generic N/A
 linux-backports-modules-4.13.0-11-generic  N/A
 linux-firmware 1.168
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-08-31 (23 days ago)
dmi.bios.date: 02/21/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81A0
dmi.board.vendor: HP
dmi.board.version: 48.54
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug artful

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

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

[Bug 1714301] Re: systemd-networkd hangs my boot (wireless)

2017-09-12 Thread Max Bowsher
Still a problem in artful upgraded from zesty right now.

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

Title:
  systemd-networkd hangs my boot (wireless)

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

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

[Bug 1716801] [NEW] Spurious creation of /stub-resolv.conf symlink

2017-09-12 Thread Max Bowsher
Public bug reported:

Code in /lib/systemd/system/systemd-resolved.service seeks to populate
/etc/resolv.conf if it is empty:

ExecStartPre=-+/bin/sh -c '[ ! -s /etc/resolv.conf ] && ln -snf
../run/systemd/resolve/stub-resolv.conf'


However the code is just wrong, and writes a symlink to /stub-resolv.conf 
rather than /etc/resolv.conf

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 00:55:32 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-16 (392 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Spectre Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-08-31 (12 days ago)
dmi.bios.date: 02/21/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81A0
dmi.board.vendor: HP
dmi.board.version: 48.54
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
modified.conffile..etc.systemd.resolved.conf: [modified]
mtime.conffile..etc.systemd.resolved.conf: 2017-09-02T14:44:21.354384

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


** Tags: amd64 apport-bug artful

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

Title:
  Spurious creation of /stub-resolv.conf symlink

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

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

[Bug 1676082] [NEW] Inactive terminator tabs have a 100% transparent background (which looks very broken)

2017-03-25 Thread Max Bowsher
Public bug reported:

In Zesty, inactive Terminator tabs now have a transparent background,
which makes the app look pretty broken.

It appears there's a default of full transparency configured in the CSS
in the code, which isn't being overridden for everything which actually
*needs* to not be transparent.

A minimal workaround seems to be:

--- 
terminator_1.90+bzr-1705-1_all.deb!/usr/share/terminator/terminatorlib/terminator.py
+++ /usr/share/terminator/terminatorlib/terminator.py   2017-03-25 
18:36:49.217215706 +
@@ -402,7 +402,7 @@
 # widgets theming may not render it's own background.
 css = """
 .terminator-terminal-window {
-background-color: alpha(@theme_bg_color,0); }
+background-color: @theme_bg_color; }
 
 .terminator-terminal-window .notebook.header {
 background-color: @theme_bg_color; }

It seems that upstream bug 1599453 may have something to do with this.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: terminator 1.90+bzr-1705-1 [modified: 
usr/share/terminator/terminatorlib/terminator.py]
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sat Mar 25 18:44:18 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-29 (1031 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: terminator
UpgradeStatus: Upgraded to zesty on 2017-03-25 (0 days ago)

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


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  Inactive terminator tabs have a 100% transparent background (which
  looks very broken)

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

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


[Bug 1629138] Re: Unity launcher doesn't recognize gnome-terminal processes as connected with launcher

2016-09-29 Thread Max Bowsher
Additionally, if I hover over the gnome-terminal title bar to show the
menus, the application menu is titled "Unknown Application Name".

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

Title:
  Unity launcher doesn't recognize gnome-terminal processes as connected
  with launcher

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

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


[Bug 1629138] [NEW] Unity launcher doesn't recognize gnome-terminal processes as connected with launcher

2016-09-29 Thread Max Bowsher
Public bug reported:

On current yakkety:

* Open the dash
* Search for the Terminal application (gnome-terminal)
* Drag-drop it to the launcher
* Click the newly added application launcher

Observe that a gnome-terminal window opens, but rather than the
application launcher having a steady illuminated background to indicate
there is a running instance, it continues to pulse until it times out.
Additionally, a *second* gnome-terminal icon appears at the bottom of
the unity launcher, where ephemeral applications not locked to the
launcher live.

I tested this in a clean newly created user account - still occurs.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
 GCC version:  gcc version 6.2.0 20160914 (Ubuntu 6.2.0-3ubuntu15)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Fri Sep 30 00:30:19 2016
DistUpgraded: 2016-09-20 22:56:19,572 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-17-generic, x86_64: installed
 nvidia-367, 367.44, 4.8.0-17-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:094e]
InstallationDate: Installed on 2014-05-29 (854 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Precision T1700
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: unity
UpgradeStatus: Upgraded to yakkety on 2016-09-20 (9 days ago)
dmi.bios.date: 04/25/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 073MMW
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/25/2014:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn073MMW:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision T1700
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Sep 30 00:28:04 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Wireless Optical Mouse® 1.0A MOUSE, id 8
 inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
xserver.errors: Error loading keymap /var/lib/xkb/server-0.xkm
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu yakkety

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

Title:
  Unity launcher doesn't recognize gnome-terminal processes as connected
  with launcher

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

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

[Bug 1624369] Re: Please sync mozc 2.18.2595.102+dfsg-1 (main) from Debian unstable (main)

2016-09-23 Thread Max Bowsher
Concerning this update... ibus-mozc seems to have stopped displaying its
suggestions window on upgrading to yakkety, which is a rather major
fault.

Upgrading to a local build of this version restores it.

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

Title:
  Please sync mozc 2.18.2595.102+dfsg-1 (main) from Debian unstable
  (main)

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

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


[Bug 1626932] [NEW] cyrus-admin installs broken symlinks to sieveshell and installsieve

2016-09-23 Thread Max Bowsher
Public bug reported:

maxb@altimeter:~$ ls -lA /usr/bin/sieveshell 
lrwxrwxrwx 1 root root 13 Jul 25 13:19 /usr/bin/sieveshell -> ../sbin/cyrus
maxb@altimeter:~$ ls -lA /usr/sbin/sieveshell 
ls: cannot access '/usr/sbin/sieveshell': No such file or directory
maxb@altimeter:~$ ls -lA /usr/lib/cyrus/bin/sieveshell 
-rwxr-xr-x 1 root root 10501 Jul 25 13:19 /usr/lib/cyrus/bin/sieveshell


It would appear the utilities have been relocated but the installed symlinks 
still point to a previous location.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cyrus-admin 2.5.9-2
ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
Uname: Linux 4.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 23 10:26:32 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-29 (847 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: cyrus-imapd
UpgradeStatus: Upgraded to yakkety on 2016-09-20 (2 days ago)

** Affects: cyrus-imapd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  cyrus-admin installs broken symlinks to sieveshell and installsieve

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd/+bug/1626932/+subscriptions

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


[Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

2016-07-18 Thread Max Bowsher
Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source
package, rebuilt it locally, and installed it. It seems to have fixed
the problem for me. So perhaps the problem really is in the Ubuntu
delta?

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions

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


[Bug 1603436] [NEW] Regression in python2.7 SRU breaks python-cassandra

2016-07-15 Thread Max Bowsher
Public bug reported:

"SRU: backport python 2.7.12 to 16.04 LTS" (bug 1591895) has caused a
regression in (at least) python-cassandra. Any attempt to connect to a
cluster fails due to:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1894, in 
_reconnect_internal
return self._try_connect(host)
  File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1921, in 
_try_connect
self_weakref = weakref.ref(self, callback=partial(_clear_watcher, 
weakref.proxy(connection)))
TypeError: ref() does not take keyword arguments

It would appear that Python 2.7.12 has made the permitted calling
conventions for weakref.ref() stricter.

See https://github.com/datastax/python-driver/pull/585 for upstream
discussion of the issue.

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: regression-update

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

Title:
  Regression in python2.7 SRU breaks python-cassandra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1603436/+subscriptions

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


[Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

2016-04-25 Thread Max Bowsher
I'm not sure if this helps, but I see pulseaudio logging an "Operation
Not Authorized" message when things do not work:

Apr 26 01:46:52 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c: 
Acquiring transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd0
Apr 26 01:46:52 zenbook pulseaudio[3346]: [pulseaudio] bluez5-util.c: Transport 
TryAcquire() failed for transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd0 
(Operation Not Authorized)

Whereas after doing the switch-to-HSP, disconnect, reconnect, switch-to-
A2DP dance to make it work, the equivalent logging is:

Apr 26 01:52:40 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c: 
Acquiring transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd2
Apr 26 01:52:40 zenbook bluetoothd[808]: 
/org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd2: fd(23) ready
Apr 26 01:52:40 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c: 
Transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd2 acquired: fd 46

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

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

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


[Bug 1562358] Re: python-googleapi is incompatible with oauth2client >= 2.x

2016-04-23 Thread Max Bowsher
This is fairly serious, as python-googleapi in Xenial is unusable as a
result.

Since updating Xenial to an new upstream version is unlikely to be
approved post-release, please see this upstream Git commit for the one-
line fix to this problem:

https://github.com/google/google-api-python-
client/pull/185/commits/8a91b92d11b453e4ef625df20ed2402b2b2b81fb

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

Title:
  python-googleapi is incompatible with oauth2client >= 2.x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-googleapi/+bug/1562358/+subscriptions

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


[Bug 774487] Re: Totem/VLC etc. goes to background when full-screen and out of focus

2015-05-23 Thread Max Bowsher
** Summary changed:

- Totem goes to background when full-screen and out of focus
+ Totem/VLC etc. goes to background when full-screen and out of focus

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

Title:
  Totem/VLC etc. goes to background when full-screen and out of focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/774487/+subscriptions

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


[Bug 774487] Re: Totem/VLC etc. goes to background when full-screen and out of focus

2015-05-23 Thread Max Bowsher
I see this with VLC too, so it's probably with any fullscreen app.

However, at least on 15.04, ticking the 'Always on top' option via the
right-click titlebar menu of the video window is an effective
workaround.

This seems to suggest it ought to be easy to fix? It's clear Unity can
draw things correctly with the 'always on top' setting, so it seems like
it just needs to understand that full-screen is very similar to 'always
on top'.

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

Title:
  Totem/VLC etc. goes to background when full-screen and out of focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/774487/+subscriptions

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


[Bug 1451572] [NEW] 'SMART error (FailedOpenDevice) detected' emails now being sent to root after removing a USB portable hard drive

2015-05-04 Thread Max Bowsher
Public bug reported:

Since upgrading from trusty to vivid, it appears that smartd has started
sending 'SMART error (FailedOpenDevice) detected' alert emails each time
a USB external hard drive is attached and then removed (subject to it
being attached long enough to be caught by smartd's polling period).

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: smartmontools 6.3+svn4002-2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May  4 22:00:28 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-29 (340 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: smartmontools
UpgradeStatus: Upgraded to vivid on 2015-03-29 (36 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  'SMART error (FailedOpenDevice) detected' emails now being sent to
  root after removing a USB portable hard drive

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

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


[Bug 1451572] [NEW] 'SMART error (FailedOpenDevice) detected' emails now being sent to root after removing a USB portable hard drive

2015-05-04 Thread Max Bowsher
Public bug reported:

Since upgrading from trusty to vivid, it appears that smartd has started
sending 'SMART error (FailedOpenDevice) detected' alert emails each time
a USB external hard drive is attached and then removed (subject to it
being attached long enough to be caught by smartd's polling period).

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: smartmontools 6.3+svn4002-2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May  4 22:00:28 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-29 (340 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: smartmontools
UpgradeStatus: Upgraded to vivid on 2015-03-29 (36 days ago)

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


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to smartmontools in Ubuntu.
https://bugs.launchpad.net/bugs/1451572

Title:
  'SMART error (FailedOpenDevice) detected' emails now being sent to
  root after removing a USB portable hard drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1451572/+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 1445947] [NEW] 'pip3 list' throws AssertionError

2015-04-19 Thread Max Bowsher
Public bug reported:

The command 'pip3 list' is broken on vivid:

maxb@altimeter:~$ pip3 list
[snip]
Exception:
Traceback (most recent call last):
  File /usr/lib/python3/dist-packages/pip/basecommand.py, line 122, in main
status = self.run(options, args)
  File /usr/lib/python3/dist-packages/pip/commands/list.py, line 80, in run
self.run_listing(options)
  File /usr/lib/python3/dist-packages/pip/commands/list.py, line 142, in 
run_listing
self.output_package_listing(installed_packages)
  File /usr/lib/python3/dist-packages/pip/commands/list.py, line 151, in 
output_package_listing
if dist_is_editable(dist):
  File /usr/lib/python3/dist-packages/pip/util.py, line 367, in 
dist_is_editable
req = FrozenRequirement.from_dist(dist, [])
  File /usr/lib/python3/dist-packages/pip/__init__.py, line 299, in from_dist
assert len(specs) == 1 and specs[0][0] == '=='
AssertionError

The problem is that the version string of python-apt is not PEP 440
compliant.  Avoiding this crash is already fixed with a one-line patch
upstream. Please consider cherry-picking
https://github.com/pypa/pip/commit/6cab71f422f2425b4d2283023c9e955f9663dde6
into Vivid's pip.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: python3-pip 1.5.6-5ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 19 16:55:24 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-29 (325 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: python-pip
UpgradeStatus: Upgraded to vivid on 2015-03-29 (20 days ago)

** Affects: python-pip (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  'pip3 list' throws AssertionError

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1445947/+subscriptions

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


[Bug 1397694] Re: System lockups with utopic kernel

2014-12-02 Thread Max Bowsher
No, I have no Thunderbolt hardware in this computer, nor will any ever
be installed.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17.4-vivid/ has so far
been successfully running for an uptime of 2 days. So far so good,
though I didn't always experience a crash within this time on the utopic
kernel.

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

Title:
  System lockups with utopic kernel

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

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


[Bug 1397694] Re: System lockups with utopic kernel

2014-12-02 Thread Max Bowsher
I've just looked back through my /var/log/kern.log and I've noticed
something strange - I can't tell for certain which reboots are due to a
system lockup (since /var/log/syslog has rotated away too much, so I
can't look for rsyslogd shutting down to identify a clean reboot), but
it looks very much as if all of the lockups have occurred shortly after
midday.

That's rather baffling.

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

Title:
  System lockups with utopic kernel

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

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


[Bug 1397694] Re: System lockups with utopic kernel

2014-12-01 Thread Max Bowsher
Dell's release notes for this BIOS update state We do not recommend you
to upgrade to A10 BIOS if your system doesn't support Thunderbolt
hardware.

I decline to install a BIOS update that the manufacture recommends
against.

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

Title:
  System lockups with utopic kernel

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

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


[Bug 1397694] [NEW] System lockups with utopic kernel

2014-11-30 Thread Max Bowsher
Public bug reported:

Since upgrading to utopic, I've been experiencing occasional system
lockups - when this occurs, nothing at all is responsive including the
mouse pointer and Alt-SysRq combinations.

Lockups only occur infrequently - perhaps once every day or two days -
so testing this is going to be slow and problematic.

So far, rolling back to the trusty kernel seems to have fixed it, so it
seems unlikely to be a hardware problem.

I'm going to reboot into http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.17.4-vivid/ now and run with that for a few days.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  maxb   3916 F pulseaudio
 /dev/snd/controlC0:  maxb   3916 F pulseaudio
CurrentDesktop: Unity
Date: Sun Nov 30 15:32:28 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=143e606d-b6a1-4350-af21-aa2f83f8d351
InstallationDate: Installed on 2014-05-29 (185 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IwConfig:
 eth0  no wireless extensions.
 
 virbr0no wireless extensions.
 
 lono wireless extensions.
MachineType: Dell Inc. Precision T1700
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic  N/A
 linux-firmware 1.138
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-11-02 (27 days ago)
dmi.bios.date: 04/25/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 073MMW
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/25/2014:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn073MMW:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision T1700
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug utopic

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

Title:
  System lockups with utopic kernel

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

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


[Bug 1382975] [NEW] utopic upgrade failure: postrm: extlinux-update: not found

2014-10-19 Thread Max Bowsher
Public bug reported:

My trusty-utopic upgrade failed due to:

Removing syslinux-themes-debian (12-3) ...
/var/lib/dpkg/info/syslinux-themes-debian.postrm: 15: 
/var/lib/dpkg/info/syslinux-themes-debian.postrm: extlinux-update: not found
dpkg: error processing package syslinux-themes-debian (--remove):
 subprocess installed post-removal script returned error exit status 127

The syslinux-themes-debian postrm should be more tolerant of other
removals.

** Affects: syslinux-themes-debian (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/1382975

Title:
  utopic upgrade failure: postrm: extlinux-update: not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux-themes-debian/+bug/1382975/+subscriptions

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


[Bug 1347834] Re: UnboundLocalError: local variable 'e' referenced before assignment in doUpdate, line 924

2014-10-18 Thread Max Bowsher
This appears to be a coding error. If you look at the file and line
referenced, you see the local variable 'e' being referenced, but it is
not in scope there.

It looks like the code is expecting the captured exception variable from
a previously exited 'except' block to still be in scope after the block
completes. It isn't.

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

Title:
  UnboundLocalError: local variable 'e' referenced before assignment in
  doUpdate, line 924

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1347834/+subscriptions

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


[Bug 1347834] Re: UnboundLocalError: local variable 'e' referenced before assignment in doUpdate, line 924

2014-10-18 Thread Max Bowsher
Further note on reproducability:

The bug is only directly visible if the previous loop attempting
multiple retries to update the APT cache fails on all attempts.

One way to make this happen is to have a third party PPA in sources.list
which doesn't have anything published for utopic, and have [Sources]
AllowThirdParty=yes set, such that the APT update fails with a 404.

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

Title:
  UnboundLocalError: local variable 'e' referenced before assignment in
  doUpdate, line 924

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1347834/+subscriptions

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


[Bug 855921] Re: does not honor netcfg/choose_interface in preseed

2014-08-23 Thread Max Bowsher
ooshlablu is correct. You cannot preseed network settings in a preseed
file which the installer is loading from a network location, because the
network needs to be configured before the preseed can be fetched.

The solution here is to pass the appropriate options on the kernel
command line.

You can either preseed the interface value directly, or you can pass the
BOOTIF option on the kernel command line, which netcfg will use.

If using pxelinux, the relevant option is IPAPPEND 2.
http://www.syslinux.org/wiki/index.php/SYSLINUX#SYSAPPEND_bitmask

I'll set this bug to status Invalid now, as it's actually a support
request on how to set up automated PXE, rather than an actual bug.

** Changed in: netcfg (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: netcfg (Ubuntu Maverick)
   Status: Confirmed = Invalid

** Changed in: netcfg (Ubuntu Natty)
   Status: Confirmed = Invalid

** Changed in: netcfg (Ubuntu Oneiric)
   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/855921

Title:
  does not honor netcfg/choose_interface in preseed

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

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


[Bug 1340734] [NEW] oem-config missing from installed system after OEM mode setup using EFI boot

2014-07-11 Thread Max Bowsher
Public bug reported:

Scenario: d-i EFI netboot with oem-config/enable=true

Problem: After the install completes and reboots into the OEM
configuration temporary user, there is no icon on the desktop to invoke
oem-config-prepare - indeed, oem-config is not even installed.

Cause: oem-config-udeb installs a finish-install.d script which runs
'apt-install oem-config-gtk ubiquity-frontend-gtk', however this fails.
It turns out to be a dependency issue. ubiquity depends on 'grub-pc |
grub | grub-efi', however grub-efi is now a dummy transitional package
and is not installed (the actual package is grub-efi-amd64). The APT
resolver makes a bad choice, and tries to install grub-pc (the BIOS boot
version), uninstalling the EFI version. This fails, leaving oem-config
not installed.

An adequate (if somewhat inelegant) solution should be to replace grub-
efi in ubiquities dependencies with all possible platform varieties of
grub-efi-ARCH.

** Affects: ubiquity (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/1340734

Title:
  oem-config missing from installed system after OEM mode setup using
  EFI boot

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

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


[Bug 1302971] [NEW] Doesn't support ID3 v2.4

2014-04-05 Thread Max Bowsher
Public bug reported:

Program appears to not support ID3 format version 2.4 - it reports no
tags present when run on such a file

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: id3v2 0.1.12-2.1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr  5 09:40:04 2014
EcryptfsInUse: Yes
SourcePackage: id3v2
UpgradeStatus: Upgraded to trusty on 2014-02-28 (36 days ago)

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

** Affects: id3v2 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug trusty

** Bug watch added: Debian Bug tracker #309278
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309278

** Also affects: id3v2 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309278
   Importance: Unknown
   Status: Unknown

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

Title:
  Doesn't support ID3 v2.4

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

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


[Bug 1289597] Re: bash: words: bad array subscript

2014-03-09 Thread Max Bowsher
** Branch linked: lp:~j/bash-completion/bug1289597

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

Title:
  bash: words: bad array subscript

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1289597/+subscriptions

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


[Bug 1289303] [NEW] Breaks completion of file paths beginning with ~/

2014-03-07 Thread Max Bowsher
Public bug reported:

On trusty, with bash-completion installed, I can't tab-complete paths to
files beginning with ~/

Only directories are offered as completion candidates.

This completion works correctly when the bash-completion package is
purged, reverting to basic built-in completion.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: bash-completion 1:2.1-2ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar  7 11:45:06 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-06-21 (259 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: bash-completion
UpgradeStatus: Upgraded to trusty on 2014-02-28 (7 days ago)

** Affects: bash-completion (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/1289303

Title:
  Breaks completion of file paths beginning with ~/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1289303/+subscriptions

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


[Bug 1289317] [NEW] New windows open at random small sizes

2014-03-07 Thread Max Bowsher
Public bug reported:

Open several terminator windows by repeatedly pressing Ctrl+Shift+I

For me, they open at a seemingly random variety of different sizes,
e.g.:

79x21
78x20
76x18
77x19
76x18

The size should be:
1) Constant
2) Based on a standard 80 character width

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: terminator 0.97-2
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar  7 12:07:03 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-06-21 (259 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: terminator
UpgradeStatus: Upgraded to trusty on 2014-02-28 (7 days ago)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  New windows open at random small sizes

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

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


[Bug 1289180] [NEW] Zoom dropdown is broken

2014-03-06 Thread Max Bowsher
Public bug reported:

Recently, within trusty, evince has broken so that the zoom selector in
the top right of the window is inoperable.

Clicking its dropdown arrow does not cause any UI to open.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu9
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar  7 07:30:30 2014
EcryptfsInUse: Yes
SourcePackage: evince
UpgradeStatus: Upgraded to trusty on 2014-02-28 (7 days ago)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  Zoom dropdown is broken

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

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


[Bug 1282203] Re: gnome-terminal not respecting Enable menu access keys setting, inside the Unity desktop environment.

2014-03-05 Thread Max Bowsher
I observe that the menu access keys are correctly disabled if
UBUNTU_MENUPROXY=0 is set in the environment, disabling the global menu
to revert to menu bar drawn within the gnome-terminal window.

Therefore, I've marked the bug as also affecting unity, as it seems
highly likely that at least some of the fix will need to be in Unity
rather than gnome-terminal.

** Also affects: unity (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/1282203

Title:
  gnome-terminal not respecting Enable menu access keys setting,
  inside the Unity desktop environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1282203/+subscriptions

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


[Bug 1286488] [NEW] Installs special EGL implementation breaking, e.g. totem

2014-03-01 Thread Max Bowsher
Public bug reported:

I installed android-tools-adbd, and was surprised when totem stopped
working.

It turns out that libhybris installs its own implementation of the
alternative /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf at a higher
priority than the one from mesa, but the libhybris one is missing
libraries such as libwayland-egl.so.1

It's clear that there's a complex interaction between packages here. It
would be nice if it didn't lead to things breaking with missing
libraries.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libhybris 0.1.0+git20131207+e452e83-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5
Uname: Linux 3.13.0-13-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar  1 09:07:48 2014
EcryptfsInUse: Yes
SourcePackage: libhybris
UpgradeStatus: Upgraded to trusty on 2014-02-28 (1 days ago)

** Affects: libhybris (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/1286488

Title:
  Installs special EGL implementation breaking, e.g. totem

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

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


[Bug 1185838] Re: Mouse pointer corruption, radeon, dual-head

2013-06-14 Thread Max Bowsher
I have just experienced the same manner of pointer corruption using the
upstream 3.10-rc5 kernel

** Tags added: kernel-bug-exists-upstream

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  Mouse pointer corruption, radeon, dual-head

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

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


[Bug 1185838] Re: Mouse pointer corruption, radeon, dual-head

2013-06-10 Thread Max Bowsher
I have spent some time trying to better quantify how often the problem
reproduces in daily use with the raring kernel, and ironically I only
experienced the problem a couple of times in a week now that I'm
actually trying to reproduce it.

I have now switched to the 3.10-rc5 mainline build, and will see what
happens.

Unfortunately, due to the random nature of whether this reproduces or
not, it will likely be two weeks before I will be able to conclude with
reasonable certainty that an absence of occurrences actually indicates
an absence of the bug. On the other hand, if the problem recurs, I'll be
able to report back sooner.

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

Title:
  Mouse pointer corruption, radeon, dual-head

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

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


[Bug 1188036] [NEW] debian-keyring is a rather heavyweight Recommends for ubuntu-dev-tools, perhaps demote to Suggests?

2013-06-06 Thread Max Bowsher
Public bug reported:

debian-keyring was promoted from a Suggests to a Recommends as a result
of a user report in bug 717245.

However, either behaviours of tools have changed since then, or there
was confusion between errors and warnings -  if I use pull-debian-source
without having debian-keyring installed on raring, the only downside is
a couple of minor warning messages printed:

gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on 
./squashfs-tools_4.2+20130409-1.dsc

but the package is unpacked successfully.


debian-keyring is a huge package (42MB .deb) compared to ubuntu-dev-tools (157K 
.deb), so I'd suggest that it be demoted to a Suggests again, given the only 
purpose is to enable an optional feature.


This is of course a somewhat a matter of opinion, so feel free to Won't Fix if 
you don't agree.

** Affects: ubuntu-dev-tools (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/1188036

Title:
  debian-keyring is a rather heavyweight Recommends for ubuntu-dev-
  tools, perhaps demote to Suggests?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1188036/+subscriptions

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


[Bug 1185838] [NEW] Mouse pointer corruption, radeon, dual-head

2013-05-30 Thread Max Bowsher
Public bug reported:

Since upgrading from quantal to raring, I am experiencing corruption of
my mouse pointer around once per day.

I am using a dual-head setup on an ATI RV730 GL [FirePro V3750].

When corruption occurs, the mouse pointer is usually some garbled
rearrangement of the pointer's pixels when the pointer is on one
monitor, becoming invisible when shifted to the other monitor.

Symptoms are a lot like
https://bugs.freedesktop.org/show_bug.cgi?id=55819 except raring's
kernel is a lot newer than the change referred to there, and I haven't
managed to locate any specific screen areas which affect the behaviour I
am seeing.

Unfortunately I am not able to reproduce corruption on demand, it just
happens from time to time during normal use.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-22-generic 3.8.0-22.33
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  maxb   4155 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Thu May 30 14:50:38 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=80c9ae73-47c4-4752-adb5-cb2014936cbb
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
 
 virbr0no wireless extensions.
MachineType: Dell Inc. Precision WorkStation T3500
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic 
root=/dev/mapper/vg0-syslv ro
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-22-generic N/A
 linux-backports-modules-3.8.0-22-generic  N/A
 linux-firmware1.106
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-03-16 (74 days ago)
WifiSyslog:
 
dmi.bios.date: 07/06/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0XPDFK
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd07/06/2012:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn0XPDFK:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug raring

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

Title:
  Mouse pointer corruption, radeon, dual-head

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

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


[Bug 1170958] Re: [Regression] Panel shadow dropped on full screen windows after notification

2013-05-18 Thread Max Bowsher
Should the Ubuntu bugtask really be marked Fix Committed when it looks
like the fix has only landed into Unity upstream branches at present?

Also, when might this reach raring-proposed?

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

Title:
  [Regression] Panel shadow dropped on full screen windows after
  notification

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1170958/+subscriptions

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


[Bug 1167622] Re: Cannot change EFI variables using efibootmgr (raring regression)

2013-04-18 Thread Max Bowsher
Hi. Sorry for taking so long to get back on this one. I failed to see
the emails due to some mail rules filing things into folders too
aggressively, which I've now fixed.

I've bisected, and come up with a hopefully useful result: the
regression occurred between 3.8.2 and 3.8.3 !

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

Title:
  Cannot change EFI variables using efibootmgr (raring regression)

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

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


[Bug 1167622] Re: Cannot change EFI variables using efibootmgr (raring regression)

2013-04-18 Thread Max Bowsher
It would appear that 9f677cf27341b7a53915ad0e018912dc022a2a24 is almost
certainly the issue (based on examining the efi commits between 3.8.2
and 3.8.3). To quote its commit message:

efi: be more paranoid about available space when creating variables

commit 68d929862e29a8b52a7f2f2f86a0600423b093cd upstream.

UEFI variables are typically stored in flash. For various reasons, avaiable
space is typically not reclaimed immediately upon the deletion of a
variable - instead, the system will garbage collect during initialisation
after a reboot.

Some systems appear to handle this garbage collection extremely poorly,
failing if more than 50% of the system flash is in use. This can result in
the machine refusing to boot. The safest thing to do for the moment is to
forbid writes if they'd end up using more than half of the storage space.
We can make this more finegrained later if we come up with a method for
identifying the broken machines.

Signed-off-by: Matthew Garrett matthew.garr...@nebula.com
Cc: Josh Boyer jwbo...@redhat.com
Signed-off-by: Matt Fleming matt.flem...@intel.com
Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

Which is understandable, but SERIOUSLY vulnerable to false positives.

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

Title:
  Cannot change EFI variables using efibootmgr (raring regression)

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

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


[Bug 1167934] [NEW] gnome-disks crashed with SIGSEGV in udisks_drive_ata_get_smart_updated()

2013-04-11 Thread Max Bowsher
Public bug reported:

I am seeing a repeatable crash in gnome-disks when unplugging a SATA HD
whilst the SMART Data window for the HD in question is open.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-disk-utility 3.6.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
NonfreeKernelModules: nfsv3 nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc 
arc4 md4 nls_utf8 cifs fscache btrfs zlib_deflate ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c reiserfs ext2 nfnetlink_log nfnetlink dm_crypt 
bnep rfcomm bluetooth binfmt_misc snd_hda_codec_analog dell_wmi coretemp 
kvm_intel kvm psmouse sparse_keymap gpio_ich snd_hda_intel tpm_tis ppdev dcdbas 
snd_hda_codec snd_hwdep snd_pcm snd_page_alloc lpc_ich snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer i7core_edac 
edac_core snd dm_multipath scsi_dh serio_raw soundcore microcode parport_pc 
mac_hid lp parport hid_generic usbhid hid usb_storage radeon i2c_algo_bit tg3 
ttm ptp drm_kms_helper ahci libahci pps_core drm wmi
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 11 14:25:58 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-disks
MarkForUpload: True
ProcCmdline: gnome-disks
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f54884a7dd7 udisks_drive_ata_get_smart_updated+23:  
mov0xf0(%rax),%rax
 PC (0x7f54884a7dd7) ok
 source 0xf0(%rax) (0x00f0) not located in a known VMA region (needed 
readable region)!
 destination %rax ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-disk-utility
StacktraceTop:
 udisks_drive_ata_get_smart_updated () from 
/usr/lib/x86_64-linux-gnu/libudisks2.so.0
 ?? ()
 ?? ()
 g_timeout_dispatch (source=source@entry=0xc9c370, callback=optimised out, 
user_data=optimised out) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:4413
 g_main_dispatch (context=0xb5d5b0) at 
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3054
Title: gnome-disks crashed with SIGSEGV in udisks_drive_ata_get_smart_updated()
UpgradeStatus: Upgraded to raring on 2013-03-16 (25 days ago)
UserGroups: adm admin arpwatch cdrom dialout libvirtd lpadmin plugdev 
sambashare sbuild sudo wireshark

** Affects: gnome-disk-utility (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace raring

** Information type changed from Private to Public

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

Title:
  gnome-disks crashed with SIGSEGV in
  udisks_drive_ata_get_smart_updated()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1167934/+subscriptions

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


[Bug 1167622] [NEW] Cannot change EFI variables using efibootmgr (raring regression)

2013-04-10 Thread Max Bowsher
Public bug reported:

Hardware: Asus Zenbook Prime UX21A

Runing quantal, I can set boot parameters using efibootmgr as expected.

Running raring, any attempt to write EFI vars fails.

dmesg says:
[  248.382221] efivars: set_variable() failed: status=8009

strace of efibootmgr says:
write(3, B\0o\0o\0t\0O\0r\0d\0e\0r\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0..., 2084) = 
-1 EIO (Input/output error)

Bug 1167567 may be related but not quite the same (I see EIO, not
ENOSPC)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-17-generic 3.8.0-17.27
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  maxb   2349 F pulseaudio
CRDA:
 country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Date: Wed Apr 10 23:59:45 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3bb6077a-27f3-44cd-b71d-fc553dea7f84
MachineType: ASUSTeK COMPUTER INC. UX21A
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=8d70d748-42b7-47f3-86d2-080fa18ca3ae ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-17-generic N/A
 linux-backports-modules-3.8.0-17-generic  N/A
 linux-firmware1.104
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-03-16 (24 days ago)
dmi.bios.date: 09/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX21A.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX21A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX21A.215:bd09/06/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX21A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug raring

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

Title:
  Cannot change EFI variables using efibootmgr (raring regression)

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

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


[Bug 1167622] Re: Cannot change EFI variables using efibootmgr (raring regression)

2013-04-10 Thread Max Bowsher
The bug also occurs with upstream 3.9-rc6 from the kernel-ppa

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

Title:
  Cannot change EFI variables using efibootmgr (raring regression)

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

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


[Bug 1165789] [NEW] Wifi indicator shows disconnected in between connecting and connected (raring regression)

2013-04-07 Thread Max Bowsher
Public bug reported:

In quantal, the network-manager indicator progressed straight from
connecting (pulsing/rippling wifi symbol) to connected (static wifi
signal level indicator) when successfully connected.

In raring, it shows the disconnected (outlined empty lack of wifi
symbol) symbol for a half-second or so between connecting and
connected, provoking a moment's concern of What? My wifi connection
failed? until the user learns to tolerate this quirk.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sun Apr  7 16:45:16 2013
EcryptfsInUse: Yes
IpRoute:
 default via 192.168.42.129 dev usb0  proto static 
 169.254.0.0/16 dev usb0  scope link  metric 1000 
 192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.195  metric 
1
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to raring on 2013-03-16 (21 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 usb0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/2  
 wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.0connected   enabled   enabled 
disabled   enabled disabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug raring

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

Title:
  Wifi indicator shows disconnected in between connecting and
  connected (raring regression)

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

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


[Bug 1024405] Re: Port to udisks2

2013-04-07 Thread Max Bowsher
It should be noted that this isn't just a backend issue. There are a
couple of user visible weirdnesses as a result:

1) USB sticks mounted by usb-creator show up at /media/deviceuuid not
/media/user/deviceuuid like removable media generally does in raring

2) Attempting to unmount via the Unity launcher shows a spurious
authentication prompt for unmounting a device mounted by a different
user, presumably because udisks 1 and udisks 2 don't talk to each
other.

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

Title:
  Port to udisks2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1024405/+subscriptions

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


[Bug 1114545] Re: Startup Disk Creator fails when erasing disk

2013-04-07 Thread Max Bowsher
*** This bug is a duplicate of bug 689593 ***
https://bugs.launchpad.net/bugs/689593

** This bug has been marked a duplicate of bug 689593
   2x100% CPU and memory usage growth when performing partition modifications 
via udisks

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

Title:
  Startup Disk Creator fails when erasing disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1114545/+subscriptions

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


[Bug 1090663] Re: erase disk results in error message + 100% CPU hang

2013-04-07 Thread Max Bowsher
*** This bug is a duplicate of bug 689593 ***
https://bugs.launchpad.net/bugs/689593

** This bug has been marked a duplicate of bug 689593
   2x100% CPU and memory usage growth when performing partition modifications 
via udisks

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

Title:
  erase disk results in error message + 100% CPU hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1090663/+subscriptions

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


[Bug 689593] Re: 2x100% CPU and memory usage growth when performing partition modifications via udisks

2013-04-07 Thread Max Bowsher
** Summary changed:

- 2x100% CPU and memory usage growth when setting bootable flag in palimpsest
+ 2x100% CPU and memory usage growth when performing partition modifications 
via udisks

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

Title:
  2x100% CPU and memory usage growth when performing partition
  modifications via udisks

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/689593/+subscriptions

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


[Bug 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal

2013-04-01 Thread Max Bowsher
The other option for people on Quantal is to upgrade to Raring. There's
still no fglrx, but the open source radeon driver has improved a *lot*.

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

Title:
  fglrx-installer not working with AMD Radeon/Mobility Radeon HD
  2000-4000 cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 1162389] [NEW] Preferences inaccessible

2013-03-30 Thread Max Bowsher
Public bug reported:

The menu option to open the Totem Preferences UI appears to have gone
missing.

There's evidence in the source code that there's supposed to be a
preferences UI, and the online help states there should be an Edit 
Preferences menu item, but it does not appear.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: totem 3.6.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sun Mar 31 00:46:48 2013
EcryptfsInUse: Yes
MarkForUpload: True
SourcePackage: totem
UpgradeStatus: Upgraded to raring on 2013-03-16 (14 days ago)

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


** Tags: amd64 apport-bug raring

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

Title:
  Preferences inaccessible

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

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


[Bug 1162389] Re: Preferences inaccessible

2013-03-30 Thread Max Bowsher
Actually, on digging around in the glade file totem.ui, it would appear
that the whole menu with id 'appmenu' is missing from the UI.

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

Title:
  Preferences inaccessible

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

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


[Bug 1158594] Re: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)

2013-03-30 Thread Max Bowsher
I think I've discovered mostly what had gone wrong - somehow in the
process of going quantal-raring, either the various colour balance
settings in totem got changed, or it changed how it interpreted the
numerical values in dconf. When I dug around in dconf-editor, I found
various colour-related settings under org.gnome.Totem, which, once reset
to defaults, caused my display issue to go away.

The problem was exacerbated by bug 1162389 - the totem preferences
dialog has become inaccessible - hence why I had to resort to dconf-
editor to change them.

Thus, this bug becomes a question of how a visually sensible colour
configuration on quantal ended up looking wrong after upgrading to
raring.

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

Title:
  Video is too yellow/bright, as if a grossly exaggerated gamma
  transform is applied (raring regression)

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

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


[Bug 1162389] Re: Preferences inaccessible

2013-03-30 Thread Max Bowsher
*** This bug is a duplicate of bug 1131754 ***
https://bugs.launchpad.net/bugs/1131754

** This bug has been marked a duplicate of bug 1131754
   [raring] Totem is missing the GNOME AppMenu functions: Open, Preferences, 
etc.

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

Title:
  Preferences inaccessible

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

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


[Bug 1160966] [NEW] PMTU discovery no longer works in Linux 3.6+ with routers that do not send next hop MTU information

2013-03-27 Thread Max Bowsher
Public bug reported:

After upgrading to raring, I found that path MTU discovery no longer worked
correctly for accessing some devices on the other side of an IPsec tunnel.

Bisection revealed the problems started with 3.6 and are still present in
3.9-rc4 (latest available at time of reporting).

Some investigation into code changes leads me to the belief that Linux lost
support for handling ICMP destination unreachable fragmentation needed packets
for which the next hop MTU field is zero. This is an expected condition when
dealing with older routers, as RFC792 originally defined ICMP destination
unreachable fragmentation needed without a next hop MTU field, and it was later
added in bytes previously allocated as unused.

The particular router in my case generating such packets is a machine running
OpenBSD 4.6.

A commit that appears to be of particular interest in this bug is
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=46517008e1168dc926cf2c47d529efc07eca85c0

I have also filed this bug in upstream kernel bugzilla as
https://bugzilla.kernel.org/show_bug.cgi?id=55861 - I'm reporting here
also to track this as a regression of raring vs. quantal.

** Affects: linux
 Importance: Unknown
 Status: Unknown

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: New


** Tags: kernel-da-key regression-release

** Bug watch added: Linux Kernel Bug Tracker #55861
   http://bugzilla.kernel.org/show_bug.cgi?id=55861

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=55861
   Importance: Unknown
   Status: Unknown

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

Title:
  PMTU discovery no longer works in Linux 3.6+ with routers that do not
  send next hop MTU information

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

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


[Bug 1160966] Re: PMTU discovery no longer works in Linux 3.6+ with routers that do not send next hop MTU information

2013-03-27 Thread Max Bowsher
I bisected only as far as I could using already built packages in the
mainline kernel-ppa.  The rest of the detail, and locating that specific
commit were done by inspecting the source and git logs.

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

Title:
  PMTU discovery no longer works in Linux 3.6+ with routers that do not
  send next hop MTU information

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

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


[Bug 916279] Re: three squares broadcast state indicator does not update when broadcast state is changed with a keybinding

2013-03-23 Thread Max Bowsher
Sorry for taking so long to respond to the above - I missed it amongst
all the other email that Launchpad sends me.

I am now running raring. The bug persists, and nothing is printed to
stdout/err having run terminator from gnome-terminal before testing the
bug.

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

Title:
  three squares broadcast state indicator does not update when
  broadcast state is changed with a keybinding

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

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


[Bug 1158594] [NEW] Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)

2013-03-21 Thread Max Bowsher
Public bug reported:

Some video files play in totem in raring appearing far too bright and
yellowish - the appearance is similar to an excessively strong
application of a gamma transform.

To reproduce:

1) Download this video from youtube (~15MB): youtube-dl -f 18
http://www.youtube.com/watch?v=rUgAgfO-16s

2) Open the downloaded file in totem, and the youtube page in a browser,
and play them side by side simultaneously. The difference should be
readily apparent, especially in the flaring on the Game of Thrones
text in the title sequence and in the desert scenery.

Other media players such as vlc, xine-ui render the video correctly.

** Affects: totem (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/1158594

Title:
  Video is too yellow/bright, as if a grossly exaggerated gamma
  transform is applied (raring regression)

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

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


[Bug 1158594] Re: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)

2013-03-21 Thread Max Bowsher
It looks like this may be a totem bug specifically, as if I launch the
same file playing simultaneously through totem, gst-launch-0.10 and gst-
launch-1.0 by executing the following in a terminal:

totem rUgAgfO-16s.mp4  gst-launch-1.0 playbin uri=file:///home/maxb
/rUgAgfO-16s.mp4  gst-launch-0.10 playbin uri=file:///home/maxb
/rUgAgfO-16s.mp4 

it is easy to see that only the totem playback displays the abnormal
colouring.

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

Title:
  Video is too yellow/bright, as if a grossly exaggerated gamma
  transform is applied (raring regression)

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

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


[Bug 1156206] [NEW] Add quantal and raring to selectable Ubuntu releases

2013-03-17 Thread Max Bowsher
Public bug reported:

unetbootin currently doesn't list quantal and raring in its selectable
options for Ubuntu.

I'm attaching the requisite trivial debdiff.

The raring options clearly won't work yet, since it's not released
(indeed, it behaves weirdly and starts downloading hardy instead) but if
we add it now, the version in raring should be able to install a raring
image once raring is released.

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

** Patch added: unetbootin-add-distroseries.debdiff
   
https://bugs.launchpad.net/bugs/1156206/+attachment/3579547/+files/unetbootin-add-distroseries.debdiff

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

Title:
  Add quantal and raring to selectable Ubuntu releases

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

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


[Bug 1156294] [NEW] Bogus config control file included in .deb

2013-03-17 Thread Max Bowsher
Public bug reported:

root@zenbook:~# dpkg-reconfigure compiz
/var/lib/dpkg/info/compiz.config: 1: /var/lib/dpkg/info/compiz.config: 
[general]: not found
/var/lib/dpkg/info/compiz.config: 2: /var/lib/dpkg/info/compiz.config: backend: 
not found
/var/lib/dpkg/info/compiz.config: 3: /var/lib/dpkg/info/compiz.config: 
plugin_list_autosort: not found
/var/lib/dpkg/info/compiz.config: 5: /var/lib/dpkg/info/compiz.config: 
[gnome_session]: not found
/var/lib/dpkg/info/compiz.config: 6: /var/lib/dpkg/info/compiz.config: backend: 
not found
/var/lib/dpkg/info/compiz.config: 7: /var/lib/dpkg/info/compiz.config: 
integration: not found
/var/lib/dpkg/info/compiz.config: 8: /var/lib/dpkg/info/compiz.config: 
plugin_list_autosort: not found
/var/lib/dpkg/info/compiz.config: 9: /var/lib/dpkg/info/compiz.config: profile: 
not found
/var/lib/dpkg/info/compiz.config: 11: /var/lib/dpkg/info/compiz.config: 
[general_ubuntu]: not found
/var/lib/dpkg/info/compiz.config: 12: /var/lib/dpkg/info/compiz.config: 
backend: not found
/var/lib/dpkg/info/compiz.config: 13: /var/lib/dpkg/info/compiz.config: 
integration: not found
/var/lib/dpkg/info/compiz.config: 14: /var/lib/dpkg/info/compiz.config: 
plugin_list_autosort: not found
/var/lib/dpkg/info/compiz.config: 15: /var/lib/dpkg/info/compiz.config: 
profile: not found

It would appear that the compiz package has included a file named config
within the debian/ directory without realizing that this filename is
picked up by dh_installdebconf. The file in the source package should be
renamed to something which does not collide with this convention.

** Affects: compiz (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/1156294

Title:
  Bogus config control file included in .deb

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

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


[Bug 1067876] Re: Missing Safely Remove Drive option from Quicklists. Only have Eject.

2013-03-04 Thread Max Bowsher
 I have Quantal on USB-flash for testing. There are 70+ users of Quantal,
 which are affected by this bug.
 As far I know Quantal is supported until 2014 April. I hope you can fix
 this bug in Quantal using another method in near future.

It doesn't sound like a very effective use of developers' time to craft
a separate temporary solution for an older release, when the problem is
so easily worked around (just choose Unmount, then manually unplug the
device). Personally, I'd rather people spent time on making Raring the
best release it can be - it's under 8 weeks to release, even.

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

Title:
  Missing Safely Remove Drive option from Quicklists. Only have
  Eject.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1067876/+subscriptions

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


[Bug 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal

2012-11-07 Thread Max Bowsher
My FirePro V5700 ceased to work with the fglrx driver with the exact
same update, in the exact same way, as described here, and has the same
underlying chip as Radeon HDs known to be affected.

The AMD website is hardly a shining example of consistency - there's an
8.982 Linux driver offered for the FirePro V5700 at
http://support.amd.com/us/Pages/AMDSupportHub.aspx if you select
Workstation Graphics and FirePro Performance Pre-WHQL Driver.

The weight of evidence is certainly sufficient to convince me that it's
all one issue. If AMD ever come up with a driver that supports the
Radeon HD [234]xxx on X server 1.13 but does not support my FirePro,
I'll reconsider.

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

Title:
  fglrx-installer not working with AMD Radeon/Mobility Radeon HD
  2000-4000 cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal

2012-11-07 Thread Max Bowsher
lspci has this to say about it:
02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV730 
[FirePro V5700]

The balance of evidence regarding the FirePro V5700 seems to be support
was dropped in 8.982, and the AMD website is just getting it wrong when
it offers 8.982.x for the FirePro V5700 in some combinations of clicking
through the driver selector forms.

The balance of evidence regarding the FireStream cards seems confused.
The PDF release notes linked from individual driver versions at
http://support.amd.com/us/gpudownload/fire/previous/Pages/fire_linux.aspx
suggest support dropped, whilst
http://support.amd.com/us/kbarticles/Pages/AMDCatalystSoftwareSuiteVersion1211BetaReleaseNotes.aspx
is contradictory to this, suggesting support continues.

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

Title:
  fglrx-installer not working with AMD Radeon/Mobility Radeon HD
  2000-4000 cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal

2012-11-06 Thread Max Bowsher
@Christopher Penalver:

Your comment-less removal of a useful part of the bug description after
the confrontations already occurred in this bug is frankly rude. I shall
add it back with additional notes.

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

Title:
  fglrx-installer not working with HD2000-4000 legacy cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal

2012-11-06 Thread Max Bowsher
** Description changed:

  Following the AMD decision to change to a new driver support model for
  Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per
  http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy-
  radeon_linux.aspx , fglrx-installer installs non-working drivers.
+ 
+ NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 
chips are affected - if your board's chip is a member of these families, you 
should consider this bug report to most likely apply to you. This includes some 
FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility 
parts which are rebadged Radeon HD4x00 parts. If unsure, please consult
+ http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. 
However there seems to be some question surrounding some FireStream parts 
containing R7xx chips, which may still be supported by the main Catalyst driver 
releases.
  
  I suggest the addition of an fglrx-legacy package to install the AMD
  legacy drivers for users with older cards or patch the current code base
  for use with these cards.
  
  Output for fglrx 9.00 [1]:
  # lspci|grep VGA
  01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
RS780L [Radeon HD 3000]
  # modprobe fglrx
  FATAL: Error inserting fglrx 
(/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device
  # dmesg|tail -n3
  [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 
7132 MBytes.
  [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
  [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
  # dpkg --list|grep fglrx
  ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators
  ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD 
graphics accelerators
  
  [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-
  updates/+bug/1032672/comments/34
  
   WARNING !!!
  The following workaround has produced mixed results and left some users with 
temporarily broken systems. It is not recommended for production systems or 
novice users that are not comfortable with basic console/non-GUI recovery. USE 
AT OWN RISK.
  WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx  sudo apt-get update 
 sudo apt-get -y upgrade  sudo apt-get -y install fglrx-legacy
  
  This workaround will downgrade X to 1.12 and install the AMD legacy
  fglrx 8.97 (Catalyst 12.6).

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

Title:
  fglrx-installer not working with HD2000-4000 legacy cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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

[Bug 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal

2012-11-06 Thread Max Bowsher
** Description changed:

  Following the AMD decision to change to a new driver support model for
  Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per
  http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy-
  radeon_linux.aspx , fglrx-installer installs non-working drivers.
  
  NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 
chips are affected - if your board's chip is a member of these families, you 
should consider this bug report to most likely apply to you. This includes some 
FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility 
parts which are rebadged Radeon HD4x00 parts. If unsure, please consult
- http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. 
However there seems to be some question surrounding some FireStream parts 
containing R7xx chips, which may still be supported by the main Catalyst driver 
releases.
+ http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. 
However there seems to be some question surrounding some FireStream parts 
containing R7xx chips, which may still be supported by the main Catalyst driver 
releases according to AMD's website, though bug 1075035 contains as yet 
inconclusive evidence counter to this.
  
  I suggest the addition of an fglrx-legacy package to install the AMD
  legacy drivers for users with older cards or patch the current code base
  for use with these cards.
  
  Output for fglrx 9.00 [1]:
  # lspci|grep VGA
  01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
RS780L [Radeon HD 3000]
  # modprobe fglrx
  FATAL: Error inserting fglrx 
(/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device
  # dmesg|tail -n3
  [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 
7132 MBytes.
  [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
  [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
  # dpkg --list|grep fglrx
  ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators
  ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD 
graphics accelerators
  
  [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-
  updates/+bug/1032672/comments/34
  
   WARNING !!!
  The following workaround has produced mixed results and left some users with 
temporarily broken systems. It is not recommended for production systems or 
novice users that are not comfortable with basic console/non-GUI recovery. USE 
AT OWN RISK.
  WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx  sudo apt-get update 
 sudo apt-get -y upgrade  sudo apt-get -y install fglrx-legacy
  
  This workaround will downgrade X to 1.12 and install the AMD legacy
  fglrx 8.97 (Catalyst 12.6).

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

Title:
  fglrx-installer not working with HD2000-4000 legacy cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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

[Bug 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal

2012-11-06 Thread Max Bowsher
@ Christopher Penalver:

Why are you so very determined to make this bug's description LESS
useful for users?

I have a FirePro V5700 [RV730] which is affected by this. The
nomenclature HD2000-4000 doesn't identify this card at all. The chip
information is vastly more useful in identifying whether a given card is
likely to be affected, yet you insist on deleting it even after I
expanded the wording to document the interesting ambiguity of the
FireStreams.

I'll put my revised wording in my comment here, since you deleted it
from the description:

--
NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 chips 
are affected - if your board's chip is a member of these families, you should 
consider this bug report to most likely apply to you. This includes some 
FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility 
parts which are rebadged Radeon HD4x00 parts. If unsure, please consult
http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. 
However there seems to be some question surrounding some FireStream parts 
containing R7xx chips, which may still be supported by the main Catalyst driver 
releases according to AMD's website, though bug 1075035 contains as yet 
inconclusive evidence counter to this.
--

As for your reluctance to refer to Wikipedia: if AMD actually provided
an official source thsat would be great. Since they don't bother,
Wikipedia is a good second best.

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

Title:
  fglrx-installer not working with HD2000-4000 legacy cards in Quantal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 945450] Re: Responsiveness: LightDM in ubuntu 12.04 very slow

2012-11-01 Thread Max Bowsher
** Tags removed: patch

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

Title:
  Responsiveness: LightDM in ubuntu 12.04 very slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/945450/+subscriptions

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


[Bug 1005642] Re: Garbage written to state file, causing slow UI

2012-11-01 Thread Max Bowsher
This bug does not appear to related to light-themes, marking bugtask
Invalid.

** Tags removed: patch

** Changed in: light-themes
   Status: Confirmed = Invalid

** Changed in: gtk
   Status: New = Invalid

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

Title:
  Garbage written to state file, causing slow UI

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1005642/+subscriptions

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


[Bug 553827] Re: Subdownloader: LookupError: unknown encoding: utf_8_valencia

2012-10-30 Thread Max Bowsher
** Summary changed:

- Subdowloader: LookupError: unknown encoding: utf_8_valencia
+ Subdownloader: LookupError: unknown encoding: utf_8_valencia

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

Title:
  Subdownloader: LookupError: unknown encoding: utf_8_valencia

To manage notifications about this bug go to:
https://bugs.launchpad.net/subdownloader/+bug/553827/+subscriptions

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


[Bug 1073369] [NEW] Ubuntu patch unconditionally breaks three-finger tap

2012-10-30 Thread Max Bowsher
Public bug reported:

The Ubuntu gnome-settings-daemon package contains a patch
disable_three_touch_tap.patch which unconditionally disables three-
finger tap.

This is annoying. I want to tap with three fingers to paste.

There's a comment mentioning some kind of gestures, but whatever they
are, nothing seems to happen on my system.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-settings-daemon 3.4.2-0ubuntu14
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
Date: Tue Oct 30 23:26:28 2012
EcryptfsInUse: Yes
MarkForUpload: True
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  Ubuntu patch unconditionally breaks three-finger tap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1073369/+subscriptions

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


[Bug 819775] Re: Broadcasting input across multiple terminator windows repeats keypresses many times

2012-10-26 Thread Max Bowsher
Oh, *right*, so that's why the problem disappeared for me. I remember
purging ibus from my system at one point, since I never use it at all.

** Changed in: terminator (Ubuntu)
   Status: Fix Released = Confirmed

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

Title:
  Broadcasting input across multiple terminator windows repeats
  keypresses many times

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

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


[Bug 1069929] [NEW] Launcher edge-reveal does not work after disabling any plugin in CCSM

2012-10-22 Thread Max Bowsher
Public bug reported:

1. Have Compiz configured for launcher auto-hide
2. Run CCSM, deactivate any plugin
3. After compiz reloads in response to the de-activation, launcher will not 
reveal in response to mouse actions
4. After running 'unity --replace ' in a gnome-terminal, launcher 
functionality is restored.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,place,regex,resize,grid,compiztoolbox,animation,snap,move,mousepoll,vpswitch,imgpng,session,workarounds,unitymtgrabhandles,wall,fade,scale,expo,unityshell]
Date: Mon Oct 22 18:15:40 2012
EcryptfsInUse: Yes
SourcePackage: unity
UpgradeStatus: Upgraded to quantal on 2012-10-12 (10 days ago)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  Launcher edge-reveal does not work after disabling any plugin in CCSM

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

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


[Bug 877438] Re: [8xxx] Unity/compiz has sluggish performance on dual-head with nvidia driver

2012-10-18 Thread Max Bowsher
This bug is very much still present on Quantal.

Environment:
Quantal, at time of release.
nvidia-current driver package.
Quadro NVS 290/PCIe/SSE2
Guest session (no significant customizations)

Simply maximizing a gnome-terminal takes more than 2 full seconds.

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

Title:
  [8xxx] Unity/compiz has sluggish performance on dual-head with nvidia
  driver

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

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


[Bug 1066324] Re: core.img too large for embedding with msdos partition style (possibly only when boot is on LVM or other complex partition type?)

2012-10-18 Thread Max Bowsher
LVM is useful on the desktop as well as the server! Can we get this
release-noted for Ubuntu Desktop too?

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

Title:
  core.img too large for embedding with msdos partition style (possibly
  only when boot is on LVM or other complex partition type?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1066324/+subscriptions

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


[Bug 1058040] Re: fglrx-installer does not support HD2000-4000 legacy cards

2012-10-16 Thread Max Bowsher
I have added an ubuntu-release-notes bugtask to this bug, because I
think it is appropriate to release-note a warning to users of older ATI
hardware that due to AMD/ATI's failure to continue to support their
hardware, they will not have the option of using fglrx after updating to
Quantal.

** Also affects: ubuntu-release-notes
   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/1058040

Title:
  fglrx-installer does not support HD2000-4000 legacy cards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 1058040] Re: fglrx-installer does not support HD2000-4000 legacy cards

2012-10-16 Thread Max Bowsher
Additionally, I'd suggest that the release notes mention the design
names i.e. R600 and R700 series as well as the marketing names, as my
hardware, which is affected, doesn't include any HD2000-4000 style
indication in its lspci output:

02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
RV730 [FirePro V5700]

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

Title:
  fglrx-installer does not support HD2000-4000 legacy cards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions

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


[Bug 1066324] Re: core.img too large for embedding with msdos partition style

2012-10-15 Thread Max Bowsher
@jcollins, jtaylor:

I am also affected by this bug and it seems to be because my disks are
all LVM, with no separate non-LVM /boot. Do your systems also match this
description?


** Also affects: ubuntu-release-notes
   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/1066324

Title:
  core.img too large for embedding with msdos partition style (possibly
  only when boot is on LVM or other complex partition type?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1066324/+subscriptions

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


[Bug 1066324] Re: core.img too large for embedding with msdos partition style

2012-10-15 Thread Max Bowsher
I have opened an ubuntu-release-notes bugtask to track adding a caution
to the Quantal release notes regarding this issue. I would imagine it
would affect every user using direct LVM booting with a traditional 62
sector embedding area between the MBR and the first partition.

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

Title:
  core.img too large for embedding with msdos partition style (possibly
  only when boot is on LVM or other complex partition type?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1066324/+subscriptions

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


[Bug 1066324] Re: core.img too large for embedding with msdos partition style

2012-10-15 Thread Max Bowsher
For the record, my workaround for this issue has been to borrow another
disc, incorporate it into my existing VG, and temporarily migrate all
data out of one existing PV at a time to allow recreating it with more
space before the partition.

Modern fdisk versions no longer default to starting the first partition
at sector 63, but choose sector 2048 instead, allowing for almost 1MiB
of grub image.

** Summary changed:

- core.img too large for embedding with msdos partition style
+ core.img too large for embedding with msdos partition style (possibly only 
boot is on LVM or other complex partition type?)

** Summary changed:

- core.img too large for embedding with msdos partition style (possibly only 
boot is on LVM or other complex partition type?)
+ core.img too large for embedding with msdos partition style (possibly only 
when boot is on LVM or other complex partition type?)

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

Title:
  core.img too large for embedding with msdos partition style (possibly
  only when boot is on LVM or other complex partition type?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1066324/+subscriptions

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


[Bug 930004] Re: update-manager assert failure: python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

2012-10-12 Thread Max Bowsher
The two machines I've upgraded from precise to quantal (yesterday 
today) have both experienced this bug, resulting in the release-upgrader
being killed, and requiring manual editing of files within
/var/lib/dpkg/ and use of aptitude to complete the upgrade.

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

Title:
  update-manager assert failure: python: ../../src/xcb_io.c:273:
  poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

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

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


[Bug 1060438] Re: wireshark crashes with ERROR:capture_dlg.c:408:capture_filter_check_syntax_cb: code should not be reached when typing a character in the capture interface field

2012-10-12 Thread Max Bowsher
The mention of pipes is just because use of pipes is pretty much the
only situation when you want to type a string into the interface
selection box.

I concur that the upstream commit you found sounds relevant.

I cannot think of any explanation why I suddenly started experiencing
this problem.

Unfortunately I have now upgraded to quantal and will not be able to
test this bug personally - I'll see if I can recruit a colleague who is
still using precise to test it.

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

Title:
  wireshark crashes with
  ERROR:capture_dlg.c:408:capture_filter_check_syntax_cb: code should
  not be reached when typing a character in the capture interface field

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

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


  1   2   3   4   5   6   7   8   9   10   >