[Bug 1246939] [NEW] package mime-support 3.54ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137

[Simon Lambourn]

Public bug reported:

I have just upgraded to Ubuntu 13.10.  
Having problems getting greeter to work with Nvidia drivers  and so booted 
linux 3.8 kernel.   Managed to login using GUI but then got this software 
problem - not sure if it is related.

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: mime-support 3.54ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Thu Oct 31 12:47:51 2013
DuplicateSignature: package:mime-support:3.54ubuntu1:subprocess installed 
post-installation script returned error exit status 137
ErrorMessage: subprocess installed post-installation script returned error exit 
status 137
MarkForUpload: True
PackageArchitecture: all
SourcePackage: mime-support
Title: package mime-support 3.54ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 137
UpgradeStatus: Upgraded to saucy on 2013-10-31 (0 days ago)

** Affects: mime-support (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package saucy

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

Title:
  package mime-support 3.54ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1246939/+subscriptions

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

[Bug 1250556] [NEW] Glade 3.8.0 and 3.14.2 crash when loading old Glade files

[Simon Lambourn]

Public bug reported:

When trying to load a .glade file created in Glade 3.8 (I think) on Oct 26 
2013, glade crashes after registering 1% progress.
This applies to both Glade 3.8.0 and 3.14.2 - both crash.
I created an extract with a message dialog object which contains the line 
child internal-child=action_area.
This also causes both version to crash when I try to load it.
(Someone on Askubuntu said that they got an error message that the child 
internal-child=vbox couldn't be found: see 
http://askubuntu.com/questions/371134/glade-is-crashing-in-ubuntu-13-10-when-i-load-a-file-done-in-ubuntu-12-04)

In addition, Glade 3.8.0 crashes when I try to create a message dialog
from an empty project file.

I did successfully create a message dialog into an empty project file
within 3.14.2, and saved/reloaded it, but was unable to load this file
into 3.8.0 - that also caused 3.8.0 to crash.

I've recently upgraded to Ubuntu 13.10, and this may be related.  The
original file would have been created in Glade 3.8 or that series as I'm
using pygtk GTK2.0 and Glade 3.14 seems to create attributes within
.glade files that the python builder doesn't recognise.

I expected that the file would be loaded OK with no crashes in any of
the scenarios above...

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: glade 3.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Nov 12 16:44:57 2013
MarkForUpload: True
SourcePackage: glade
UpgradeStatus: Upgraded to saucy on 2013-10-31 (12 days ago)

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


** Tags: amd64 apport-bug saucy

** Attachment added: original file which caused the crash
   
https://bugs.launchpad.net/bugs/1250556/+attachment/3906602/+files/mlimport.glade

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

Title:
  Glade 3.8.0 and 3.14.2 crash when loading old Glade files

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

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

[Bug 1250556] Re: Glade 3.8.0 and 3.14.2 crash when loading old Glade files

[Simon Lambourn]

Hi, I have just seen that this bug is also reported as
https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1242865 for Glade
3.14.2.  I have downloaded the ppa and this fixes 3.14.2.

However 3.8.0 is still broken.

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

Title:
  Glade 3.8.0 and 3.14.2 crash when loading old Glade files

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

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

[Bug 1242865] Re: Glade can't work with dialog windows

[Simon Lambourn]

This problem also happens with Glade 3.8.0 (the version which works with GTK 
2.0 ... I know but it works with pygtk)
The ppa fix seems to work with Glade 3.14.2 but has not fixed Glade 3.8.0

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

Title:
  Glade can't work with dialog windows

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

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

[Bug 1250556] Re: Glade 3.8.0 and 3.14.2 crash when loading old Glade files

[Simon Lambourn]

Will this patch also fix the bug with glade 3.8.0? 
This is the patch for 3.14.2: 
https://git.gnome.org/browse/glade/patch/?id=d2c8e008e1b81d501b30c070d492959da6922992

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

Title:
  Glade 3.8.0 and 3.14.2 crash when loading old Glade files

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

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

Re: [Bug 1246939] Re: package mime-support 3.54ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137

[Simon Lambourn]

Hello Charles,
Sorry for the short reply - I have just had an operation and can't sit down
at my PC at the moment.

I think you are right about the root FS. It did get full and the upgrade to
13.10 failed. I had to clear the apt package cache and then it was ok.

I'm not aware of any other errors in dmesg though.   There were some udev
related errors but I have fixed those with help from Google!

The system is working fine now.
Let me know if you need to know anything else.

Simon.

Simon Lambourn. 07952 932 823
Sent from my Android smartphone.
On 23 Nov 2013 03:05, Charles Plessy ple...@debian.org wrote:

 Dear Simon,

 in the ‘Df.txt’ file that you submitted, I note that your root
 filesystem is almost entirely full (97 %), could that be the problem ?
 I also note some strange errors in the ‘Dmseg.txt’ file. Do you
 experience other problems with your computer, that are not related to
 mime-support ?

 Cheers,

 --
 Charles Plessy
 Tsurumi, Kanagawa, Japan

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1246939

 Title:
   package mime-support 3.54ubuntu1 failed to install/upgrade: subprocess
   installed post-installation script returned error exit status 137

 Status in “mime-support” package in Ubuntu:
   Confirmed

 Bug description:
   I have just upgraded to Ubuntu 13.10.
   Having problems getting greeter to work with Nvidia drivers  and so
 booted linux 3.8 kernel.   Managed to login using GUI but then got this
 software problem - not sure if it is related.

   ProblemType: Package
   DistroRelease: Ubuntu 13.10
   Package: mime-support 3.54ubuntu1
   ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
   Uname: Linux 3.8.0-32-generic x86_64
   NonfreeKernelModules: nvidia
   ApportVersion: 2.12.5-0ubuntu2.1
   Architecture: amd64
   Date: Thu Oct 31 12:47:51 2013
   DuplicateSignature: package:mime-support:3.54ubuntu1:subprocess
 installed post-installation script returned error exit status 137
   ErrorMessage: subprocess installed post-installation script returned
 error exit status 137
   MarkForUpload: True
   PackageArchitecture: all
   SourcePackage: mime-support
   Title: package mime-support 3.54ubuntu1 failed to install/upgrade:
 subprocess installed post-installation script returned error exit status 137
   UpgradeStatus: Upgraded to saucy on 2013-10-31 (0 days ago)

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1246939/+subscriptions


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

Title:
  package mime-support 3.54ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1246939/+subscriptions

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

[Bug 1311104] [NEW] nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build

[Simon Lambourn]

Public bug reported:

I have just installed ubuntu 14.04 on amd64 hardware, and nouveau is unstable 
with my NVIDIA Geforce 8200 integrated graphics.
Tried to install nvidia-331 using sudo apt-get install nvidia-331, but the 
build failed along with the dkms build (and I think something else later).

The error messages during the build were:
Error! Bad return status for module build on kernel: 3-13.0-24-generic (x86-64)
Consult /var/lib/dkms/nvidia-331/331.38/build/make.log for more information
Error! Bad return status for module build on kernel: 3-13.0-24-generic (x86-64)
Consult /var/lib/dkms/bbswitch/0.7/build/make.log for more information

I've also tried downloading and installing the nvidia driver direct from
nvidia: this also fails with a different build error message

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 3.13.0-24-generic
Date: Tue Apr 22 14:00:34 2014
DuplicateSignature: 
dkms:nvidia-331:331.38-0ubuntu7:/var/lib/dkms/nvidia-331/331.38/build/conftest/macros.h:1:2:
 error: #error INIT_WORK() conftest failed!
PackageVersion: 331.38-0ubuntu7
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check trusty

** Attachment added: /var/lib/dkms/nvidia-331/331.38/build/make.log
   https://bugs.launchpad.net/bugs/1311104/+attachment/4092563/+files/make.log

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

Title:
  nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1311104/+subscriptions

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

[Bug 1311104] Re: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build

[Simon Lambourn]

Here is the other make.log showing the bbswitch build error

** Attachment added: /var/lib/dkms/bbswitch/0.7/build/make.log
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1311104/+attachment/4092569/+files/make.log

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

Title:
  nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1311104/+subscriptions

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

[Bug 1311121] [NEW] bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

[Simon Lambourn]

Public bug reported:

I have just installed ubuntu 14.04 as a clean install on amd64 hardware.  The 
nouveau driver is unstable with my nvidia Geforce 8200 integrated graphics, so 
installed the nvidia-331 package, using apt-get install nvidia-331.
dkms also failed to build (separate bug reported) as did bbswitch.

This bug may be similar to bug #1283461
https://bugs.launchpad.net/bugs/1283461 which relates to a slightly
different kernel version.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bbswitch-dkms (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 3.13.0-24-generic
Date: Tue Apr 22 14:00:42 2014
PackageVersion: 0.7-2ubuntu1
SourcePackage: bbswitch
Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

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

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

[Bug 1375194] [NEW] lightdm session constantly switches screen appearance

[Simon Lambourn]

Public bug reported:

After installing regular software updates on 23 Sept, my screen session
has become almost unusable.  The screen appearance (font, button
style, window menu bar location) alternates about twice a second between
my usual settings and what I guess are the default un-decorated
settings.   This means that text, buttons, and input areas are often
moving around on the screen as the font size changes or the window menu
bar comes and goes.

In addition, keyboard input characters take a variable time to appear (up to a 
few seconds?) and can appear in the wrong order.
CPU utilisation is much higher when I am logged on.   See TOP output below.   I 
get the same problems with any one of Chromium, Firefox, Thunderbird, Ubuntu 
Software Centre, BASH terminal window.

When I first sign on, I get a message system software problem detected
in a panel by itself, before the desktop is displayed, and again after
the desktop is displayed.  This is connected with the bug, but I can't
find out the details of the error.   I have selected report the
problem repeatedly.

The software installed on 23 Sept included Dbus , libdbus-1-3,  and
dbus-x11 versions 1.6.18-0ubuntu4.2.  I tried downgrading these 3 to
-0ubuntu4 but the problem remained after a reboot.   There were about
20-30 packages updated at the same time, including linux-image, but I
can't spot which might be causing the problem.   I'm using a clean
install of ubuntu 14.04 but with my /home directory from an older ubuntu
installation.


TOP output:
24974 simon 20   0 2357692 181696  65696 R  27.6  4.5   2:34.62 software-c+ 
 2253 root  20   0  279028  58104  19416 S  26.6  1.4   3:19.18 Xorg
11096 simon 20   0 1391072 186192  81872 R  22.9  4.6   5:02.98 chromium-b+ 
 3899 simon 20   0  719408  32324  17924 R  19.9  0.8   2:55.82 hud-service 
17259 simon 20   0 1036360 203656  48764 R  17.9  5.0   2:47.82 thunderbird 
 4291 simon 20   0 1591956 113836  41064 S  11.6  2.8   1:20.75 compiz  
 5857 simon 20   0  860872  76324  14440 S   5.3  1.9   1:09.93 gnome-term+ 
 3915 simon 20   0  590728  71048  10796 S   2.7  1.8   0:41.92 ibus-ui-gt+ 
 3918 simon 20   0  769636  73648  11544 S   2.7  1.8   0:42.82 unity-pane+ 
 4402 simon 20   0  511960  71072  12024 S   2.7  1.8   0:41.36 nm-applet   
 7212 simon 20   0  847244  67792  12680 S   2.7  1.7   0:37.13 update-not+ 
 3865 simon 20   0  666200  67632   7956 S   2.3  1.7   0:37.61 bamfdaemon  
 3911 simon 20   0  906492  68264   7816 S   2.3  1.7   0:38.02 gnome-sess+ 
 4130 simon 20   0  776980  67892   8080 S   2.3  1.7   0:36.34 indicator-+ 
 4146 simon 20   0  499124  66596   8156 S   2.3  1.6   0:35.04 indicator-+ 
 4410 simon 20   0  405976  73952   9800 S   2.3  1.8   0:34.70 smart-noti+ 
 4194 simon 20   0  391836  65148   7236 S   2.0  1.6   0:35.79 notify-osd

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
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
Date: Mon Sep 29 10:06:59 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2127]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=/dev/mapper/vg1-rootfs ro nodmraid nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0507
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System 

[Bug 1375194] Re: lightdm session constantly switches screen appearance

[Simon Lambourn]

Update:  I have found a workaround by .config/compiz-1 and .config/dconf
(I have a backup of the .config/dconf if this might help to debug this
issue, but not the compiz one, sorry).   This makes the screen behave
normally again...

** Attachment added: .xsession-errors shows a whole multitude of problems 
starting with at-spi2-registryd respawning too fast, then indicator-sound 
aborting, then unity-settings-daemon aborting ...
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1375194/+attachment/4221901/+files/.xsession-errors.old

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

Title:
  lightdm session constantly switches screen appearance

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

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

Re: [Bug 1311104] Re: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build [macros.h:1:2: error: #error INIT_WORK() conftest failed!]

[Simon Lambourn]

Hi Max,

Thanks for the email.
I did check and my default GCC is set to 4.8, so that wasn't the problem.
I can't install from the NVIDIA website or from the repos.  Both fail 
with a compilation error - an unknown function.

Simon

On 10/06/14 13:52, Max Mustermann wrote:
 I'm not sure whether this is related to this bug but I was unable to install 
 nvidia drivers because my default compiler was set to an older version as 
 default (gcc 4.4). Setting the default back to 4.8 solved the problem and I 
 was able to install the drivers.
 I found this bug report because I got a similar error message when trying to 
 manually install the proprietary nvidia drivers. When installing from the 
 repos I didn't get an error message 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/1311104

Title:
  nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
  [macros.h:1:2: error: #error INIT_WORK() conftest failed!]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1311104/+subscriptions

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

[Bug 1375194] Re: lightdm session constantly switches screen appearance

[Simon Lambourn]

Edit to above comment:   ... workaround by DELETING
.config/compiz-1...

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

Title:
  lightdm session constantly switches screen appearance

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

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

Re: [Bug 1311121] Re: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

[Simon Lambourn]

Dear Peter,

Thank you for investigating this bug and reporting back.   I can confirm 
that installing the linux-generic package allowed the nvidia drivers, 
and bbswitch, to compile, but I now have another problem with the nvidia 
drivers.  I think this is because I built the system without the 
linux-generic package - so I'm going back and starting again.But I 
confirm that your diagnosis about the bbswitch bug is correct.

Thanks very much for your help and I'm sorry that I didn't notice this 
myself.

Best regards
Simon Lambourn

On 25/07/14 09:57, Peter Wu wrote:
 It appears that you have linux-headers-3.13.0-24 installed, but not
 linux-headers-3.13.0-24-generic. Install the linux-generic package to
 ensure that you always stay up-to-date with recent kernels including the
 headers.

 Please re-open if the problem still persists after doing so.

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


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

Title:
  bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

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

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

[Bug 1311104] Fwd: Re: [Bug 1311121] Re: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

[Simon Lambourn]

PS.   The problem occurred because I built a ubuntu image using 
vmbuilder and installing linux-image-generic + ubuntu-desktop packages.
I am surprised that ubuntu-desktop doesn't pre-req linux-generic? Is 
this something I should report as a bug?

Simon


 Original Message 
Subject:Re: [Bug 1311121] Re: bbswitch-dkms 0.7-2ubuntu1: bbswitch 
kernel module failed to build
Date:   Mon, 28 Jul 2014 15:06:27 +0100
From:   Simon Lambourn simon.lambo...@gmail.com
To: Bug 1311121 1311...@bugs.launchpad.net


Dear Peter,

Thank you for investigating this bug and reporting back.   I can confirm
that installing the linux-generic package allowed the nvidia drivers,
and bbswitch, to compile, but I now have another problem with the nvidia
drivers.  I think this is because I built the system without the
linux-generic package - so I'm going back and starting again.But I
confirm that your diagnosis about the bbswitch bug is correct.

Thanks very much for your help and I'm sorry that I didn't notice this
myself.

Best regards
Simon Lambourn

On 25/07/14 09:57, Peter Wu wrote:
 It appears that you have linux-headers-3.13.0-24 installed, but not
 linux-headers-3.13.0-24-generic. Install the linux-generic package to
 ensure that you always stay up-to-date with recent kernels including the
 headers.

 Please re-open if the problem still persists after doing so.

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


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

Title:
  nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
  [macros.h:1:2: error: #error INIT_WORK() conftest failed!]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1311104/+subscriptions

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

[Bug 1450897] [NEW] Banshee menu bar fails to display

[Simon Lambourn]

Public bug reported:

I have had this problem intermittently with earlier releases of Ubuntu (I did a 
clean install of 14.10 but it didn't fix it).
With 15.04, Banshee has *never* displayed the menu bar (File Edit ... Tools 
Help - I can't remember exactly what it says).   
This problem still happens whether I ask for the menu bar to be shown in the 
desktop title bar, or the window title bar in Settings - Appearance.

This means I can't do a re-scan of my music and pick up any tracks added
while Banshee wasn't running - effectively making Banshee unusable by
me.   Expected behaviour: display the menu bar

Banshee release is 2.9.0+really2.6.2-2ubuntu4

Let me know if there's anything else I can do to help find out what's
going wrong.

Hope you can help!! thanks in anticipation.
Simon Lambourn

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: banshee 2.9.0+really2.6.2-2ubuntu4
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: Fri May  1 20:43:35 2015
ExecutablePath: /usr/lib/banshee/Banshee.exe
InterpreterPath: /usr/bin/mono-sgen
SourcePackage: banshee
UpgradeStatus: Upgraded to vivid on 2015-04-24 (6 days ago)

** Affects: banshee (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/1450897

Title:
  Banshee menu bar fails to display

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

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

[Bug 1450743] [NEW] Banshee in Ubuntu 15.04 VERY slow to open (24 mins)

[Simon Lambourn]

Public bug reported:

I've just upgraded to Ubuntu 15.04 and Banshee has become unusably slow to open.
I have a big music database (42,000 tracks) and this used to take maybe a 
minute to open.  Now it is 24 minutes: the first few times I thought it was 
never going to open!

The problem may be similar to a bug reported for Red Hat 
https://bugzilla.redhat.com/show_bug.cgi?id=1161844
which was thought to be related to different treatment of an ANALYZE statement 
by Sqlite 3.8.7

My system has banshee 2.9.0+really2.6.2-2ubuntu4 and sqlite3 3.8.7.4-1

Let me know if there's any other information you need -  thanks in
advance for your help.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: banshee 2.9.0+really2.6.2-2ubuntu4
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: Fri May  1 10:09:06 2015
ExecutablePath: /usr/lib/banshee/Banshee.exe
InterpreterPath: /usr/bin/mono-sgen
SourcePackage: banshee
UpgradeStatus: Upgraded to vivid on 2015-04-24 (6 days ago)

** Affects: banshee (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/1450743

Title:
  Banshee in Ubuntu 15.04 VERY slow to open (24 mins)

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

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

[Bug 1447956] Re: Banshee interface unresponsive after upgrade to 15.04

[Simon Lambourn]

I tried to install the updated package from vivid-proposed but apt-get
was going to remove loads of important packages as part of the upgrade,
so I didn't go ahead with the installation.  Is there something wrong
with the package dependencies, or is it me??

I followed the instructions in
https://wiki.ubuntu.com/Testing/EnableProposed to add vivid-proposed and
allow selective installation from it.   trying apt-get upgrade -s  found
no packages for upgrade

But when I did apt-get install banshee/vivid-proposed, I got the
following output:

$ sudo apt-get install banshee/vivid-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '2.9.0+really2.6.2-2ubuntu5' (Ubuntu:15.04/vivid-proposed 
[amd64]) for 'banshee'
Selected version '2.44.1-1ubuntu1' (Ubuntu:15.04/vivid-proposed [amd64]) for 
'libglib2.0-0' because of 'banshee'
Selected version '2.9.0+really2.6.2-2ubuntu5' (Ubuntu:15.04/vivid-proposed 
[amd64]) for 'banshee-extension-soundmenu' because of 'banshee'
The following packages were automatically installed and are no longer required:
  app-install-data apt-xapian-index gir1.2-gmenu-3.0 laptop-detect
  oneconf-common python-characteristic python-cups python-debtagshw
  python-dirspec python-httplib2 python-idna python-oneconf python-openssl
  python-pam python-piston-mini-client python-pyasn1 python-pyasn1-modules
  python-serial python-service-identity python-twisted-bin python-twisted-core
  python-twisted-web python-zope.interface python3-oneconf
  python3-piston-mini-client software-center-aptdaemon-plugins
  ubuntuone-client-data
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  banshee-extension-soundmenu libglib2.0-0
Suggested packages:
  gstreamer1.0-ffmpeg banshee-dbg
The following packages will be REMOVED
  libatk-bridge2.0-dev libatk1.0-dev libatspi2.0-dev libcairo2-dev
  libdbus-glib-1-dev libgdk-pixbuf2.0-dev libglade2-dev libglib2.0-bin
  libglib2.0-dev libgtk-3-dev libgtk2.0-dev libpango1.0-dev lightdm oneconf
  python-gobject-2-dev python-gtk2-dev python-ubuntu-sso-client
  software-center ubuntu-desktop ubuntu-settings ubuntu-sso-client
  ubuntu-sso-client-qt unity unity-tweak-tool
The following packages will be upgraded:
  banshee banshee-extension-soundmenu libglib2.0-0
3 to upgrade, 0 to newly install, 24 to remove and 0 not to upgrade.
Need to get 3,849 kB of archives.
After this operation, 70.7 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

Without the reference to vivid-proposed, apt-get autoremove shows 0 to
remove.

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

Title:
  Banshee interface unresponsive after upgrade to 15.04

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

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

[Bug 1447956] Re: Banshee interface unresponsive after upgrade to 15.04

[Simon Lambourn]

Help please!   I'm still trying to install the proposed fix from vivid-
proposed.  It has clearly worked for others so I must be getting the
command wrong.   My 15.04 system is a clean install of 14.10  then
recently updated, so it should be straightforward.

When I try apt-get install banshee/vivid-proposed, it proposes to remove
loads of packages including unity and software-center (see above).  I
didn't continue with this.

When I try apt-get install banshee=2.9.0+really2.6.2-2ubuntu5   I get:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 banshee : Depends: libglib2.0-0 (= 2.44.1) but 2.44.0-1ubuntu3 is to be 
installed
   Recommends: banshee-extension-soundmenu (= 
2.9.0+really2.6.2-2ubuntu5) but 2.9.0+really2.6.2-2ubuntu4 is to be installed
E: Unable to correct problems, you have held broken packages.

It seems you can't combine package=version and package/target-release,
as apt-get install banshee=2.9.0+really2.6.2-2ubuntu5/vivid-proposed
doesn't find the package.   I can see the package is available using
apt-cache policy banshee.

Clearly I'm doing it wrong, but I can't work out what is wrong .. .sorry
- can anyone advise what the correct command to install the fix should
be please?

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

Title:
  Banshee interface unresponsive after upgrade to 15.04

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

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

[Bug 1447956] Re: Banshee interface unresponsive after upgrade to 15.04

[Simon Lambourn]

Will this fix be available for the current release of Ubuntu, Vivid
Vervet (15.04)?   I see it has been released for Wily which I guess is
15.10, not yet released.

Alternatively, is there a way of downloading the fixed package
2.9.0+really2.6.2-3ubuntu1 into Vivid/15.04?   Otherwise, it can't be
said to be fixed in the currently available Ubuntu...

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

Title:
  Banshee interface unresponsive after upgrade to 15.04

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

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

Re: [Bug 1447956] Re: Banshee interface unresponsive after upgrade to 15.04

[Simon Lambourn]

Thank you!(I won't put this on Launchpad...)
Simon

On 27/05/15 20:13, Chow Loong Jin wrote:
 On Wed, May 27, 2015 at 06:03:45PM -, Simon Lambourn wrote:
 Will this fix be available for the current release of Ubuntu, Vivid
 Vervet (15.04)?   I see it has been released for Wily which I guess is
 15.10, not yet released.

 Alternatively, is there a way of downloading the fixed package
 2.9.0+really2.6.2-3ubuntu1 into Vivid/15.04?   Otherwise, it can't be
 said to be fixed in the currently available Ubuntu...
 Yes, I'll upload it to Vivid as well. It just needs to enter Wily first, 
 because
 Stable Release Updates cannot be uploaded before the fix is confirmed to work 
 on
 the current development release.


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

Title:
  Banshee interface unresponsive after upgrade to 15.04

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

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

[Bug 1516723] [NEW] Crash when using 'Move to' ...

[Simon Lambourn]

Public bug reported:

When using Nautilus to move a folder, or a few folders, to somewhere else, 
Nautilus sometimes crashes, although it has already done the move by that 
stage.   The window disappears to be replaced by the "Ubuntu has had a problem, 
do you want to report it?" dialogue.
When you try to re-open Nautilus by right-clicking on the icon the favourites 
are not displayed - they re-appear after you have opened Nautilus.

Sometimes this crash happens, sometimes it doesn't, and I can't see that
I am doing anything different each time (usually moving a folder of mp3
& flac files from one place to another on my PC).   Maybe one time in 5
it crashes?  But that means I have experienced lots of crashes, as I use
this feature a lot.   It has not just happened in the latest release but
has been happening for some time.


Incidentally - the 'about' page doesn't mention Nautilus as the name of the 
product.  You could be forgiven for thinking that it's called Files.  So if you 
are not getting many bug reports, that could be one reason...

Let me know if I can provide other information.  Thanks for your help
with this, in anticipation.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.14.2-0ubuntu13
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 16 17:15:07 2015
GsettingsChanges:
 
SourcePackage: nautilus
UpgradeStatus: Upgraded to wily on 2015-10-25 (21 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  Crash when using 'Move to' ...

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

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

[Bug 1664675] [NEW] Rosegarden "open file" dialog fails with .rg files, works if file specified on launch

[Simon Lambourn]

Public bug reported:

Rosegarden fails to open files (using the "file open" button or
"File/Recent" menu selection) with a popup window "Cannot open
"   Screenshot attached.

However the same files can be opened by double-clicking on them in Nautilus.
Let me know if you need more info.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: rosegarden 1:16.06-1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 14 19:10:50 2017
SourcePackage: rosegarden
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (122 days ago)

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1664675/+attachment/4818960/+files/Screenshot%20from%202017-02-14%2019-12-00.png

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

Title:
  Rosegarden "open file" dialog fails with .rg files, works if file
  specified on launch

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

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

[Bug 1633871] Re: Mythtv frontend stuck in restart loop (code 139) after update to Ubuntu 16.10

[Simon Lambourn]

Thankyou Thomas.  It appears to work for me (one test only).  I'll
report back if I have any problems.

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

Title:
  Mythtv frontend stuck in restart loop (code 139) after update to
  Ubuntu 16.10

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

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

Re: [Bug 1629131] Re: Unable to use 'filething' to open files in mutagen.mp3.MP3

[Simon Lambourn]

Christoph,
Don't worry - it was an interesting exercise.   I've upgraded from your
PPA, and I look forward to trying it out.
Simon

On Fri, 30 Sep 2016 at 10:01 Christoph Reiter <1629...@bugs.launchpad.net>
wrote:

> No problem. The docs should have a note mentioning when it was
> introduced I guess.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1629131
>
> Title:
>   Unable to use 'filething' to open files in mutagen.mp3.MP3
>
> Status in mutagen package in Ubuntu:
>   Invalid
>
> Bug description:
>   Hi,  I have been trying to 'override' the file open parameters in the
>   MP3 module to improve scan performance of a large music library, using
>   python3-mutagen.
>
>   I can't get the supplied example to work: I get the following output:
>
>   $ python3 fileobj-gio.py
>   Traceback (most recent call last):
> File "fileobj-gio.py", line 130, in 
>   print(mutagen.File(mutagen_file).pprint())
> File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 239, in
> File
>   with open(filename, "rb") as fileobj:
>   TypeError: invalid file: <__main__.GioMutagenFile object at
> 0x7f204fba4be0>
>
>   Looking through the code I can't see how it would treat a 'file-like
>   object' any differently: it seems that open(filename,"rb") will always
>   be called.
>
>   What I want to achieve is to understand if different buffering would
>   improve elapsed time to scan large numbers of files.  I was hoping to
>   open the file first using different buffering parameter and pass a
>   file-object to MP3, but the only documented way of doing this using
>   open() is by passing the fileno() attribute of an already open file,
>   which also fails on the open statement:
>
>   m=MP3(f.fileno())
>   Traceback (most recent call last):
> File "", line 1, in 
> File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 42, in
> __init__
>   self.load(filename, *args, **kwargs)
> File "/usr/lib/python3/dist-packages/mutagen/id3/__init__.py", line
> 1092, in load
>   with open(filename, "rb") as fileobj:
>   OSError: [Errno 9] Bad file descriptor
>
>   Any advice would be most welcome on either how to fix the bug or other
>   ways to improve scan performance.   Thanks for your help.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: python3-mutagen 1.31-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
>   Uname: Linux 4.4.0-38-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Fri Sep 30 00:03:20 2016
>   Dependencies:
>
>   PackageArchitecture: all
>   SourcePackage: mutagen
>   UpgradeStatus: Upgraded to xenial on 2016-04-22 (160 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mutagen/+bug/1629131/+subscriptions
>

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

Title:
  Unable to use 'filething' to open files in mutagen.mp3.MP3

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

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

Re: [Bug 1629131] Re: Unable to use 'filething' to open files in mutagen.mp3.MP3

[Simon Lambourn]

Aaah!   So much time spent trying different ways of getting this to work
and such a simple mistake!
Thank you for the quick reply, and I'm sorry to have bothered you with this.

Great package...
Simon

On Fri, 30 Sep 2016 at 08:35 Christoph Reiter <1629...@bugs.launchpad.net>
wrote:

> File like object support was added in 1.33.
>
> You can get the newest version in my PPA if needed:
> https://launchpad.net/~lazka/+archive/ubuntu/ppa
>
> If you find anything else please report it upstream:
> https://github.com/quodlibet/mutagen/issues
>
> ** Changed in: mutagen (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1629131
>
> Title:
>   Unable to use 'filething' to open files in mutagen.mp3.MP3
>
> Status in mutagen package in Ubuntu:
>   Invalid
>
> Bug description:
>   Hi,  I have been trying to 'override' the file open parameters in the
>   MP3 module to improve scan performance of a large music library, using
>   python3-mutagen.
>
>   I can't get the supplied example to work: I get the following output:
>
>   $ python3 fileobj-gio.py
>   Traceback (most recent call last):
> File "fileobj-gio.py", line 130, in 
>   print(mutagen.File(mutagen_file).pprint())
> File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 239, in
> File
>   with open(filename, "rb") as fileobj:
>   TypeError: invalid file: <__main__.GioMutagenFile object at
> 0x7f204fba4be0>
>
>   Looking through the code I can't see how it would treat a 'file-like
>   object' any differently: it seems that open(filename,"rb") will always
>   be called.
>
>   What I want to achieve is to understand if different buffering would
>   improve elapsed time to scan large numbers of files.  I was hoping to
>   open the file first using different buffering parameter and pass a
>   file-object to MP3, but the only documented way of doing this using
>   open() is by passing the fileno() attribute of an already open file,
>   which also fails on the open statement:
>
>   m=MP3(f.fileno())
>   Traceback (most recent call last):
> File "", line 1, in 
> File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 42, in
> __init__
>   self.load(filename, *args, **kwargs)
> File "/usr/lib/python3/dist-packages/mutagen/id3/__init__.py", line
> 1092, in load
>   with open(filename, "rb") as fileobj:
>   OSError: [Errno 9] Bad file descriptor
>
>   Any advice would be most welcome on either how to fix the bug or other
>   ways to improve scan performance.   Thanks for your help.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: python3-mutagen 1.31-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
>   Uname: Linux 4.4.0-38-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Fri Sep 30 00:03:20 2016
>   Dependencies:
>
>   PackageArchitecture: all
>   SourcePackage: mutagen
>   UpgradeStatus: Upgraded to xenial on 2016-04-22 (160 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mutagen/+bug/1629131/+subscriptions
>

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

Title:
  Unable to use 'filething' to open files in mutagen.mp3.MP3

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

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

[Bug 1629131] [NEW] Unable to use 'filething' to open files in mutagen.mp3.MP3

[Simon Lambourn]

Public bug reported:

Hi,  I have been trying to 'override' the file open parameters in the
MP3 module to improve scan performance of a large music library, using
python3-mutagen.

I can't get the supplied example to work: I get the following output:

$ python3 fileobj-gio.py
Traceback (most recent call last):
  File "fileobj-gio.py", line 130, in 
print(mutagen.File(mutagen_file).pprint())
  File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 239, in File
with open(filename, "rb") as fileobj:
TypeError: invalid file: <__main__.GioMutagenFile object at 0x7f204fba4be0>

Looking through the code I can't see how it would treat a 'file-like
object' any differently: it seems that open(filename,"rb") will always
be called.

What I want to achieve is to understand if different buffering would
improve elapsed time to scan large numbers of files.  I was hoping to
open the file first using different buffering parameter and pass a file-
object to MP3, but the only documented way of doing this using open() is
by passing the fileno() attribute of an already open file, which also
fails on the open statement:

m=MP3(f.fileno())
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 42, in __init__
self.load(filename, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/mutagen/id3/__init__.py", line 1092, in 
load
with open(filename, "rb") as fileobj:
OSError: [Errno 9] Bad file descriptor

Any advice would be most welcome on either how to fix the bug or other
ways to improve scan performance.   Thanks for your help.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: python3-mutagen 1.31-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 30 00:03:20 2016
Dependencies:
 
PackageArchitecture: all
SourcePackage: mutagen
UpgradeStatus: Upgraded to xenial on 2016-04-22 (160 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Unable to use 'filething' to open files in mutagen.mp3.MP3

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

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

[Bug 1633871] [NEW] Mythtv frontend stuck in restart loop (code 139) after update to Ubuntu 16.10

[Simon Lambourn]

Public bug reported:

After updating to Ubuntu 16.10, Mythtv frontend will not shut down - it
appears to function normally but on exit (normal exit at my request),
there is an onscreen notification "the frontend has crashed unexpectedly
(exit code 139).  Restarting, please wait ..." and the frontend
restarts.

This was working without problems on 16.04.  I read that this is due to
timezone problems??   The backend is on the same PC as the frontend so
should see the same timezone.  I can't see any error messages in the log
(frontend or backend) either.

Any advice or help welcomed...

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: mythtv 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 15:48:45 2016
Installed_mythtv_dbg: 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
PackageArchitecture: all
SourcePackage: mythtv
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (1 days ago)

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


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

** Attachment added: "Frontend log"
   
https://bugs.launchpad.net/bugs/1633871/+attachment/4761980/+files/mythfrontend.log

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

Title:
  Mythtv frontend stuck in restart loop (code 139) after update to
  Ubuntu 16.10

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

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

[Bug 1649957] [NEW] update-manager "show details" only opens a 1 line display

[Simon Lambourn]

Public bug reported:

When I click on the "details" option while installing software updates,
the window expands to a good size but the actual terminal display
(showing apt or dpkg output) is limited to only 1 line in height, so you
can't really see what is going on.  Expanding the window doesn't affect
the size of the terminal display.

Expected behaviour: the terminal display showing the output should
expand to fill the window size, so you can read more than one line of
what's happening.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: update-manager 1:16.10.7
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Dec 14 16:55:44 2016
GsettingsChanges:
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'569'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'window-width' b'815'
 b'com.ubuntu.update-manager' b'launch-time' b'1481732940'
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (60 days ago)

** Affects: update-manager (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/1649957

Title:
  update-manager "show details" only opens a 1 line display

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

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

[Bug 1675466] [NEW] Comment tag in flac files is not imported correctly

[Simon Lambourn]

Public bug reported:

If you export a flac file in Audacity (with a comment tag) and then re-
import it, the comment field is not picked up.   Perhaps due to
confusion over whether the tag is called "comment" or "comments": the
tag is saved as COMMENTS.   Minor impact I realise, but annoying if you
use Audacity to edit lots of flac files, as I do.

Steps to reproduce the bug:
- Create a snippet of audio in audacity
- Export as flac.  Fill in the comments field and (for example) the artist 
field.
- Now open the created flac file in Audacity
- Export it to flac again.   You will see that the artist field is pre-filled 
from the saved tags, but the comment field is blank.

Expected behaviour:  comment field should be pre-filled just like the
other fields.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: audacity 2.1.2-1build1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 23 15:53:12 2017
SourcePackage: audacity
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (159 days ago)

** Affects: audacity (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/1675466

Title:
  Comment tag in flac files is not imported correctly

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

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

[Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[Simon Lambourn]

I can repeatably get this problem if I boot without a network connection.I 
get the message "waiting for a start job to complete ... Raise Network 
Interfaces" followed by "NMI Watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[swapper/1:0]"
Booting with a network cable attached has no problems.
This is on 4.10.0-26 and AMD Athlon 64 X2, using an AMD GPU.  Nouveau module is 
not loaded.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

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

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

[Bug 1623856] Re: Scrolled Windows in update-manager are too small to read

[Simon Lambourn]

I'm seeing exactly the same behaviour as Hrunting above on 17.04. It is
an improvement on the previous one-line display but still not using the
whole window.  Additionally, when I try and vary the size of the window,
the window changes size but the "terminal-like" part of the window
doesn't change size - it stays at something like half the original size
of the window.

Identical versions of aptdaemon & update-manager to Hrunting.

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

Title:
  Scrolled Windows in update-manager are too small to read

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

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

[Bug 1726073] Re: Failed upgrade to Zesty - Could not calculate the upgrade

[Simon Lambourn]

Looks as if the main.log was already attached - let me know if you need
it.  term.log is empty.

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

Title:
  Failed upgrade to Zesty - Could not calculate the upgrade

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

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

[Bug 1726073] [NEW] Failed upgrade to Zesty - Could not calculate the upgrade

[Simon Lambourn]

Public bug reported:

Trying to upgrade from 17.04 to 17.10, I am getting the message "Could
not calculate the upgrade".

I have seen the bug 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1069160 
which seems similar, but refers to earlier releases (and is marked as invalid), 
so I am reporting a fresh bug.   Bug 1069160 was resolved by a couple of people 
by removing xserver-xorg-video-nouveau,
which I also have installed, but attempting to remove this will also remove 
xserver-xorg-video-all, and then makes a whole list of xserver-xorg-packages 
"no longer required", including the one for my graphics card - so I am 
reluctant to remove this package.

I cannot work out whether I have unsupported packages which are
preventing calculation of the upgrade (I had a look through the apt.log
but couldn't work out where the error was).

Thanks in advance for your help.   I've attached the apt.log file, and
will attach the main.log file in a comment.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-release-upgrader-core 1:17.04.10
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity:Unity7
Date: Sun Oct 22 17:25:42 2017
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to zesty on 2017-10-22 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "/var/log/dist-upgrade/apt.log"
   https://bugs.launchpad.net/bugs/1726073/+attachment/4985590/+files/apt.log

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

Title:
  Failed upgrade to Zesty - Could not calculate the upgrade

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

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

[Bug 1737445] Re: release upgrader doesn't re-enable updates after failure

[Simon Lambourn]

I'm really sorry but I have failed to re-create the bug on my own
system.   As I didn't discover the problem for at least a month, I can't
remember exactly when it occurred or what I did to make it happen.   I
do remember that after the first attempt to upgrade, there was a problem
with using the "revert" button on the Software Sources application,
which re-enabled all the Artful sources even though I hadn't upgraded -
so I had to manually alter the /etc/apt/sources.list to go back to
Zesty.   I'm pretty sure that I would have enabled all the Zesty sources
including updates, as the sources.list is not that complicated.

However I can't tell you how this happened, so regrettably I think I
have to withdraw the bug report (or at least ask you to do so).   I
apologise for wasting your time on this one.

** Attachment added: "/etc/apt/sources.list"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1737445/+attachment/5023303/+files/sources.list

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

Title:
  release upgrader doesn't re-enable updates after failure

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

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

[Bug 1768648] [NEW] Bionic obsoletes sbackup, makes restore impossible

[Simon Lambourn]

Public bug reported:

With no warning in the release notes (as far as I could see), upgrading to 
Bionic has removed and prevented re-installation of Simple Backup, sbackup.   
A message "Removed, Core functionality" or something similar, was presented in 
the "remove packages" detail screen.

However this seems to prevent restoration of any backups created by
Simple Backup.   So not only do users have to configure a different
backup solution, they have also lost access to all their backup history.

Was this considered, and if so is there some guidance available to
affected users?   If not, there probably should be, at least to recover
or migrate the backups.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.17
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 21:03:32 2018
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

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

Title:
  Bionic obsoletes sbackup, makes restore impossible

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

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

Re: [Bug 1737445] Re: release upgrader doesn't re-enable updates after failure

[Simon Lambourn]

Thankyou for putting the time into this Brian.
Much appreciated.

On Thu, 15 Feb 2018 at 21:35 Brian Murray  wrote:

> I did an audit of the release upgrader code and found a couple of spots
> where the upgrade may not have been rolled back to the previous release
> and fixed them here.
>
> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-
> upgrader/trunk/revision/3102
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737445
>
> Title:
>   release upgrader doesn't re-enable updates after failure
>
> Status in ubuntu-release-upgrader package in Ubuntu:
>   Expired
> Status in ubuntu-release-upgrader source package in Bionic:
>   Expired
>
> Bug description:
>   If a release upgrade fails (my example is in a failure to calculate
>   the upgrade: https://bugs.launchpad.net/bugs/1726180) the software
>   sources are reset but updates are not re-enabled,   This has meant in
>   my case going a month without updates, which introduces a security
>   exposure to my system.
>
>   In my case, the first two updates on the "Updates" tab of software
>   sources should have been re-enabled (zesty-security and zesty-
>   updates), but were not.
>
>   Expected behaviour:  if the release upgrader cannot complete the
>   upgrade, it should reinstate the software sources as they were prior
>   to the upgrade.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: ubuntu-release-upgrader-core 1:17.04.10
>   ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
>   Uname: Linux 4.10.0-38-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu4.9
>   Architecture: amd64
>   CrashDB: ubuntu
>   CurrentDesktop: Unity:Unity7
>   Date: Sun Dec 10 23:00:41 2017
>   PackageArchitecture: all
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: ubuntu-release-upgrader
>   UpgradeStatus: Upgraded to zesty on 2017-12-09 (1 days ago)
>   VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1737445/+subscriptions
>
-- 

Sent from my phone.  07952 932 823

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

Title:
  release upgrader doesn't re-enable updates after failure

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

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

[Bug 1726180] Re: Unable to upgrade to artful with nvidia-libopencl1-304 and virt-viewer installed

[Simon Lambourn]

Is there a workaround for this by uninstalling virt-viewer?  Will I be
able to reinstall it after the upgrade?  I am not sure what the
dependency issue is...

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

Title:
  Unable to upgrade to artful with nvidia-libopencl1-304 and virt-viewer
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1726180/+subscriptions

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

[Bug 1768648] Re: Bionic obsoletes sbackup, makes restore impossible

[Simon Lambourn]

Thankyou Anton for your helpful comments.
This may not be the place to discuss this, but has anyone tried Areca backup 
(http://www.areca-backup.org/)?  It seems to have most of the same function in 
terms of include/exclude, incremental backup etc.

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

Title:
  Bionic obsoletes sbackup, makes restore impossible

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

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

[Bug 1664675] Re: Rosegarden "open file" dialog fails with .rg files, works if file specified on launch

[Simon Lambourn]

Thanks for the response.  I have just tested it again with the release
in Ubuntu 18.04 (Rosegarden 16.06?) and I agree, it's now working fine.

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

Title:
  Rosegarden "open file" dialog fails with .rg files, works if file
  specified on launch

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

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

[Bug 1664675] Re: Rosegarden "open file" dialog fails with .rg files, works if file specified on launch

[Simon Lambourn]

Oops ... I realise that my release is 17.10 not 18.04 (which is not yet 
released).
Rosegarden version is 16.06.

I confirm that the bug is fixed on 17.10 (Rosegarden 16.06)...  
Apologies for my mistake, and thankyou for fixing it.

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

Title:
  Rosegarden "open file" dialog fails with .rg files, works if file
  specified on launch

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

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

[Bug 1835421] [NEW] EasyID3.RegisterTextKey(..., 'COMM') fails on retrieve

[Simon Lambourn]

Public bug reported:

EasyID3.RegisterTextKey('comment', 'COMM') actually defines a frame
called 'COMM::XXX', which can't be retrieved by the same name.

You can set this field as follows

>>> e = EasyID3()
>>> e['comment'] = 'a comment'
>>> vars(e)
{'_EasyID3__id3': {'COMM::XXX': COMM(encoding=, lang='XXX', 
desc='', text=['a comment'])}}

but attempting to retrieve it causes a KeyErrror:'COMM'

Code:
>>> e['comment']
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/mutagen/easyid3.py", line 213, in 
__getitem__
return func(self.__id3, key)
  File "/usr/lib/python3/dist-packages/mutagen/easyid3.py", line 121, in getter
return list(id3[frameid])
  File "/usr/lib/python3/dist-packages/mutagen/_util.py", line 536, in 
__getitem__
return self.__dict[key]
KeyError: 'COMM'

As a workaround, if I define a second text key
>>> EasyID3.RegisterTextKey('comment2', 'COMM::XXX')
I can now retrieve the original tag

>>> vars(e)
{'_EasyID3__id3': {'COMM::XXX': COMM(encoding=, lang='XXX', 
desc='', text=['a comment'])}}
>>> e['comment2']
['a comment']

Expected behaviour:e['comment'] returns 'a comment'

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: python3-mutagen 1.40.0-2
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  4 15:13:27 2019
Dependencies:
 
PackageArchitecture: all
SourcePackage: mutagen
UpgradeStatus: Upgraded to disco on 2019-04-25 (70 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  EasyID3.RegisterTextKey(...,'COMM') fails on retrieve

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

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

[Bug 1835771] Re: MP4 fails with string argument for freeform text ('----') tags

[Simon Lambourn]

PS. The use case for this is in storing and retrieving musicbrainz ID
tags, which are stored as freeform tags.

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

Title:
  MP4 fails with string argument for freeform text ('') tags

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

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

[Bug 1835771] [NEW] MP4 fails with string argument for freeform text ('----') tags

[Simon Lambourn]

Public bug reported:

mutagen.mp4.MP4 container does not accept a string value for freeform
text tags, but expects (and returns) a bytes argument.  This is
inconsistent with python3 default of string values.

code:
>>> import mutagen.mp4.MP4 as MP4
>>> m = MP4()
>>> m[':test:item'] = 'test value'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/mutagen/_file.py", line 75, in 
__setitem__
self.tags[key] = value
  File "/usr/lib/python3/dist-packages/mutagen/mp4/__init__.py", line 375, in 
__setitem__
self._render(key, value)
  File "/usr/lib/python3/dist-packages/mutagen/mp4/__init__.py", line 391, in 
_render
return render_func(self, key, value, *render_args)
  File "/usr/lib/python3/dist-packages/mutagen/mp4/__init__.py", line 632, in 
__render_freeform
data += v
TypeError: can't concat str to bytes
>>> m[':test:item'] = b'test value'
>>> m[':test:item']
b'test value'
>>> 

Expected behaviour:  accept (and return) string values, with encoding to
utf-8 if required (this is implied in some of the comments in the code).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: python3-mutagen 1.40.0-2
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  8 15:03:10 2019
Dependencies:
 
PackageArchitecture: all
SourcePackage: mutagen
UpgradeStatus: Upgraded to disco on 2019-04-25 (74 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  MP4 fails with string argument for freeform text ('') tags

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

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

[Bug 1841426] [NEW] mypy erroneously reports no [mypy] section in config file unless --config-file is specified

[Simon Lambourn]

Public bug reported:

Using mypy 0.670 installed via pip.
I created a file~/.config/mypy/config/mypy.ini containing a [mypy] section and 
one setting (mypy_path).

If I use python3 -m mypy [module to check]
I get an error:

[~]/.config/mypy/config: No [mypy] section in config file

Whereas if I use python3 -m mypy [module to check] --config-file 
~/.config/mypy/config/mypy.ini
there is no error message and the config file is processed.

Expected behaviour:
No error message if the file contains a [mypy] section

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: mypy (not installed)
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 26 12:07:42 2019
SourcePackage: mypy
UpgradeStatus: Upgraded to disco on 2019-04-25 (123 days ago)

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


** Tags: amd64 apport-bug disco

** Attachment added: "mypy.ini file"
   https://bugs.launchpad.net/bugs/1841426/+attachment/5284687/+files/mypy.ini

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

Title:
  mypy erroneously reports no [mypy] section in config file unless
  --config-file is specified

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

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

[Bug 1835771] Re: MP4 fails with string argument for freeform text ('----') tags

[Simon Lambourn]

Christoph - thank you for the pointer.   I have reported it as you
suggest: https://github.com/quodlibet/mutagen/issues/391

** Bug watch added: github.com/quodlibet/mutagen/issues #391
   https://github.com/quodlibet/mutagen/issues/391

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

Title:
  MP4 fails with string argument for freeform text ('') tags

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

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

[Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

[Simon Lambourn]

Thank you Olivier.   Yes, I forgot that I should have named "chromium-
browser" rather than "chromium" when submitting the bug report.

I agree that there could have been problems when upgrading the old
chromium browser using apt, but when using apt, the upgrade is user-
initiated, and the user is informed that chromium is going to be
upgraded.  What makes the situation worse with the snap, is that as far
as I recall, the upgrade happens without user knowledge or involvement.
I don't recall being prompted to upgrade anything, it just seemed to
happen automatically and invisibly, until I couldn't access my browser.
It's the lack of info to the user that makes this particularly annoying.

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

Title:
  snap cannot be run while being upgraded − no user feedback

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

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

[Bug 1850282] [NEW] Chromium disappears from system on refresh

[Simon Lambourn]

Public bug reported:

I've just upgraded to Ubuntu 19.10 with the new snap version of Chromium
a week or two ago

On starting my system today, I found that Chromium had disappeared from
the launcher and wasn't even in the apps list.   using the command
'chromium' didn't work either, giving me the message that chromium
wasn't installed.   "You can install it using snap install chromium".
Then when I try to install it, I get the message "chromium is already
installed".

After about 10 minutes of digging around, I discovered that the chromium
snap was disabled.  I couldn't enable it because it was being refreshed.

Come on!  this is unacceptable behaviour for any tool but especially a
browser which must be one of the most heavily used applications on
Ubuntu.  This will really hit the reputation of ubuntu with any user who
has to take maybe more than 10 minutes to discover the problem, or may
never discover it - Chromium may just mysteriously reappear some time
later.

Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

$ snap info chromium
name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more
  stable way for all Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: stable
channels:
  stable:78.0.3904.70 2019-10-29 (920) 160MB -
  candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
  beta:  78.0.3904.70 2019-10-22 (907) 165MB -
  edge:  79.0.3941.4  2019-10-21 (905) 159MB -
installed:   78.0.3904.70(917) 167MB disabled

** Affects: chromium-browser (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/1850282

Title:
  Chromium disappears from system on refresh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850282/+subscriptions

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

[Bug 1850282] Re: Chromium disappears from system on refresh

[Simon Lambourn]

(And just to add insult to injury - you can't even report a bug using
ubuntu-bug chromium!  You get an error message saying "this is produced
by Canonical - for help visit .  The url is not
properly clickable, perhaps because Chromium is not working, and you
can't select it and copy it into another browser.)

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

Title:
  Chromium disappears from system on refresh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850282/+subscriptions

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

[Bug 1865364] [NEW] SELECT WHERE using COLLATE NOCASE fails using multiple tests and using IN(...)

[Simon Lambourn]

Public bug reported:

COLLATE NOCASE seems to be ignored when using the following constructs
in a WHERE clause:

Col=value1 COLLATE NOCASE OR Col=value2
Col IN(value COLLATE NOCASE) 
Col IN(value) COLLATE NOCASE   [both are accepted, not sure which is valid 
syntax]

It works in the simple case Col=value1 COLLATE NOCASE

I have written a simple test script which demonstrates working queries
and failing queries, which is attached, and reproduced here:

# demo of sqlite bug with collate nocase
# usage: sqlite3 :memory:
# > .read sqlite_nocase_bug.sql
#
create temp table test (col text unique);
insert into test (col) values('Test');

select '1:', * from test where col='Test';  -- works
select '2:', * from test where col='test' collate nocase; -- works
select '3:', * from test where col='test' collate nocase or col='other' collate 
nocase;  -- returns no rows
select '4:', * from test where col in ('test') collate nocase; -- returns no 
rows
select '5:', * from test where col in ('test' collate nocase); -- returns no 
rows

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: sqlite3 3.29.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  1 18:17:53 2020
SourcePackage: sqlite3
UpgradeStatus: Upgraded to eoan on 2019-10-23 (129 days ago)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Script with sql statements to demonstrate bug"
   
https://bugs.launchpad.net/bugs/1865364/+attachment/5332361/+files/sqlite_nocase_bug.sql

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

Title:
  SELECT WHERE using COLLATE NOCASE fails using multiple tests and using
  IN(...)

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

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

[Bug 1863518] Re: Menuitems with actions cannot be set sensitive when in popup menus (using Glade/Python)

[Simon Lambourn]

Glade file to go with the python file

** Attachment added: "Glade file to go with the python code"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863518/+attachment/5328759/+files/menuitem_action_bug.glade

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

Title:
  Menuitems with actions cannot be set sensitive when in popup menus
  (using Glade/Python)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863518/+subscriptions

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

[Bug 1863518] [NEW] Menuitems with actions cannot be set sensitive when in popup menus (using Glade/Python)

[Simon Lambourn]

Public bug reported:

The bug may be assigned to the wrong package: I'm using Glade 3.22.1 and
Python 3.7.5.

Using popup menus, if I assign Gio.Actions to the menuitems, the menuitems 
become insensitive, so you cannot click on them, even if they have a handler 
for the "activate" signal as well.
I can assign Gio.Actions successfully to menuitems in a menubar, or a drop_down 
menu attached to a menubar, or to other clickable widgets such as buttons, so I 
think the logic works.

The Glade xml output looks as if it is correctly specified (although I'm
no expert), so I guess that Gtk.Builder is not connecting the signals
properly.   Or there might be a restriction that I'm not aware of... so
apologies if I am trying to do something not supported, but I have tried
to research this.

Behaviour:  menuitems in popup menus that have actions assigned are
always insensitive and cannot be made sensitive.

Expected behaviour:   menuitems in popup menus that have actions
assigned should be sensitive and activatable.

I have attached the python and glade code which demonstrate the problem.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libgtk-3-0 3.24.12-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 16 20:37:22 2020
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to eoan on 2019-10-23 (115 days ago)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "Python code to demonstrate the problem"
   
https://bugs.launchpad.net/bugs/1863518/+attachment/5328752/+files/menuitem_action_bug.py

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

Title:
  Menuitems with actions cannot be set sensitive when in popup menus
  (using Glade/Python)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863518/+subscriptions

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

[Bug 1872209] [NEW] syntax error message in f-string doesn't report line number

[Simon Lambourn]

Public bug reported:

I accidentally came across this annoying 'feature' or more likely, bug.

The following code 
   f"...foo ... {**kwargs} ..."
produces a very basic syntax error message with no line number in the source 
file:

  File "", line 1
(**kwargs)
  ^
SyntaxError: invalid syntax


This is the error message I would expect from the interpreter, but not when 
running a python script.   A demo script is as follows: 

''' f-string bug demonstration '''

def main(*args, **kwargs):
print(f"main() called with *args={*args}, **kwargs={**kwargs}")

With a longer python file, it is hard to find the offending line.
Should the line number be displayed in the error message?

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python3 3.7.5-1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 11 17:08:35 2020
SourcePackage: python3-defaults
UpgradeStatus: Upgraded to eoan on 2019-10-23 (170 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  syntax error message in f-string doesn't report line number

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1872209/+subscriptions

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

[Bug 1875596] [NEW] Django Timefield(default=) gives unhelpful diagnostics

[Simon Lambourn]

Public bug reported:

(Be warned, I am a novice and this may be a novice mistake):

I mistakenly added a TimeField instead of a DurationField to my model.
I was forced to give it a default value and chose TimeDelta(minutes=30).
The makemigration worked, but the migrate command crashed with very
unhelpful diagnostics, not even indicating which field caused the
problem.

I'm hoping that this lack of diagnostics could be improved, to at least
point to the database column that caused the problem?

Thanks in advance for all the good stuff you do :-)
Simon Lambourn.


Output from manage.py migrate:

Operations to perform:
  Apply all migrations: admin, auth, contenttypes, kitten, sessions
Running migrations:
  Applying kitten.0010_auto_20200428_0957...Traceback (most recent call last):
  File "manage.py", line 22, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
utility.execute()
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 356, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
283, in run_from_argv
self.execute(*args, **cmd_options)
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
330, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", 
line 204, in handle
fake_initial=fake_initial,
  File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 
115, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, 
fake_initial=fake_initial)
  File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 
145, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, 
fake_initial=fake_initial)
  File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 
244, in apply_migration
state = migration.apply(state, schema_editor)
  File "/usr/lib/python3/dist-packages/django/db/migrations/migration.py", line 
129, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, 
project_state)
  File 
"/usr/lib/python3/dist-packages/django/db/migrations/operations/fields.py", 
line 88, in database_forwards
field,
  File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/schema.py", 
line 240, in add_field
self._remake_table(model, create_field=field)
  File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/schema.py", 
line 115, in _remake_table
self.effective_default(create_field)
  File "/usr/lib/python3/dist-packages/django/db/backends/base/schema.py", line 
245, in effective_default
default = field.get_db_prep_save(default, self.connection)
  File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", 
line 770, in get_db_prep_save
prepared=False)
  File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", 
line 2281, in get_db_prep_value
value = self.get_prep_value(value)
  File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", 
line 2276, in get_prep_value
return self.to_python(value)
  File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", 
line 2250, in to_python
parsed = parse_time(value)
  File "/usr/lib/python3/dist-packages/django/utils/dateparse.py", line 76, in 
parse_time
match = time_re.match(value)
TypeError: expected string or bytes-like object

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python3-django 1:1.11.22-1ubuntu1.3
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 09:59:25 2020
PackageArchitecture: all
SourcePackage: python-django
UpgradeStatus: Upgraded to eoan on 2019-10-23 (187 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Django Timefield(default=) gives unhelpful diagnostics

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

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

[Bug 1875596] Re: Django Timefield(default=) gives unhelpful diagnostics

[Simon Lambourn]

Dear Rafael,
Thank you for responding to my bug report.   I'm sorry I didn't provide the 
full information you ask for, and based on your feedback I'm not sure whether 
this is a bug or not.  It is certainly a user error, but the bug I'm hoping to 
raise is with the unhelpful diagnostics, rather than my own mistake.  

I've provided more info below.   I would be grateful if you could take a
look and decide whether this qualifies as a bug - then based on your
advice I will be happy to re-open the bug or not.

Steps to reproduce the bug:
- Define a model class as follows
class Test(models.Model):
testfield = models.TimeField(default=datetime.timedelta(0))
# I acknowledge this is a user error but it is accepted by Python, and 
by makemigration.

= run makemigration (which works OK) and migrate (which fails, giving
the output described above).

Desired output:
An error message from the migrate command, stating that a TypeError occurred 
setting a value to this field, with either model name/field name, or a source 
line number.

Thanks again for your advice.

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

Title:
  Django Timefield(default=) gives unhelpful diagnostics

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

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

[Bug 2067895] [NEW] Mythtv can no longer access DVB devices after ubuntu 24.04 upgrade

[Simon Lambourn]

Public bug reported:

Before upgrade, mythtv was working with two separate DVB tuners.
After upgrade, mythtv can see the /dev/dvb adapters but cannot access them 
("could not get card info for /dev/dvb/adapter0/frontend0").  All recordings 
since the upgrade to ubuntu 24.04 have failed.

The devices seem to have the right permissions and mythtv-backend is
running as mythtv, which is a member of the video group:

ls -al /dev/dvb/adapter?
/dev/dvb/adapter0:
total 0
drwxr-xr-x  2 root root 120 Jun  3 10:21 .
drwxr-xr-x  4 root root  80 Jun  3 10:21 ..
crw-rw+ 1 root video 212, 1 Jun  3 10:21 demux0
crw-rw+ 1 root video 212, 2 Jun  3 10:21 dvr0
crw-rw+ 1 root video 212, 0 Jun  3 10:21 frontend0
crw-rw+ 1 root video 212, 3 Jun  3 10:21 net0

/dev/dvb/adapter1:
total 0
drwxr-xr-x  2 root root 120 Jun  3 10:21 .
drwxr-xr-x  4 root root  80 Jun  3 10:21 ..
crw-rw+ 1 root video 212, 5 Jun  3 10:21 demux0
crw-rw+ 1 root video 212, 6 Jun  3 10:21 dvr0
crw-rw+ 1 root video 212, 4 Jun  3 10:21 frontend0
crw-rw+ 1 root video 212, 7 Jun  3 10:21 net0

lsof /dev/dvb   and fuser /dev/dvb do not report any users of the
devices (I hope I am using the command correctly)

Expected behaviour:   mythtv can access the DVB tuners and use them for
live TV & recordings, as previously.

Ubuntu is now 24.04 Noble Numbat, after upgrading from 23.10.
Mythtv is now 2:34.0+fixes.20240210.e3e165a1-0ubuntu6

I am using the web frontend to access mythtv backend setup.
mythbackend.log has the following entries:

2024-06-03T10:56:06.285978+01:00 gracix2 mythbackend: mythbackend[2706]: E 
HTTP0 cardutil.cpp:1249 (OpenVideoDevice) CardUtil: Can't open DVB frontend 
(/dev/dvb/adapter0/frontend0) for 
/dev/dvb/adapter0/frontend0.#012#011#011#011eno: Device or resource busy (16)
2024-06-03T10:56:06.448387+01:00 gracix2 mythbackend: mythbackend[2706]: E 
HTTP0 cardutil.cpp:928 (ProbeCurrentDeliverySystem) CardUtil: open failed 
(/dev/dvb/adapter0/frontend0)#012#011#011#011eno: Device or resource busy (16)
2024-06-03T10:56:06.448744+01:00 gracix2 mythbackend: mythbackend[2706]: E 
HTTP0 cardutil.cpp:1249 (OpenVideoDevice) CardUtil: Can't open DVB frontend 
(/dev/dvb/adapter1/frontend0) for 
/dev/dvb/adapter1/frontend0.#012#011#011#011eno: Device or resource busy (16)
2024-06-03T10:56:06.449107+01:00 gracix2 mythbackend: mythbackend[2706]: E 
HTTP0 cardutil.cpp:928 (ProbeCurrentDeliverySystem) CardUtil: open failed 
(/dev/dvb/adapter1/frontend0)#012#011#011#011eno: Device or resource busy (16)

It says the device is busy, but as far as I can tell there is nothing
using the device?

Thank you in advance for any help.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: mythtv 2:34.0+fixes.20240210.e3e165a1-0ubuntu6
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  3 10:57:46 2024
Installed_mythtv_dbg: 0.0
PackageArchitecture: all
SourcePackage: mythtv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble third-party-packages wayland-session

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

Title:
  Mythtv can no longer access DVB devices after ubuntu 24.04 upgrade

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


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

[Bug 2067895] Re: Mythtv can no longer access DVB devices after ubuntu 24.04 upgrade

[Simon Lambourn]

dmesg output:

$ sudo dmesg |grep dvb
[   21.100050] saa7134_dvb: dvb_init() allocating 1 frontend
[   21.248215] em28xx 2-2:1.0: dvb set to isoc mode.
[   21.596207] dvbdev: DVB: registering new adapter (saa7130[0])
[   21.596232] dvbdev: dvb_create_media_entity: media entity 'NXP TDA10048HN 
DVB-T' registered.
[   21.599068] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' 
registered.
[   21.724204] tda10048_firmware_upload: waiting for firmware upload 
(dvb-fe-tda10048-1.0.fw)...
[   30.545497] dvbdev: DVB: registering new adapter (2-2:1.0)
[   30.545509] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs 
Si2168' registered.
[   30.547906] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' 
registered.
[   30.551147] em28xx: Registered (Em28xx dvb Extension) extension
[   78.147389] si2168 11-0064: downloading firmware from file 
'dvb-demod-si2168-b40-01.fw'
[   78.845473] si2168 11-0064: downloading firmware from file 
'dvb-demod-si2168-b40-01.fw'

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

Title:
  Mythtv can no longer access DVB devices after ubuntu 24.04 upgrade

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


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