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
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
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
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
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.
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
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
(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
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
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
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
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
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
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=,
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
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.
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
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
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
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.
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
: 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
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
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
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
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
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
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
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
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
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
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)
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.
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
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
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,
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
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
55 matches
Mail list logo