Public bug reported:
Affects linux kernels 5.13+ (21.10 uses 5.13).
See: https://github.com/openzfs/zfs/issues/12712
Patch to backport into linux-modules that should fix issue:
https://github.com/openzfs/zfs/pull/12759
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package:
** Summary changed:
- Broken CURL support with GDC
+ libphobos: std.net.curl does not understand HTTP/2 status lines
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876293
Title:
libphobos:
I believe this is the relevant upstream phobos issue.
https://issues.dlang.org/show_bug.cgi?id=19367
Patch can be applied cleanly enough to gcc sources.
https://patch-diff.githubusercontent.com/raw/dlang/phobos/pull/6752.diff
** Bug watch added: issues.dlang.org/ #19367
Done https://gitlab.com/openconnect/openconnect/-/issues/121
** Bug watch added: gitlab.com/openconnect/openconnect/-/issues #121
https://gitlab.com/openconnect/openconnect/-/issues/121
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Package: network-manager-openconnect
Version: 1.2.4-1ubuntu1
Priority: optional
Section: universe/net
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Mike Miller
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 84.0 kB
Depends: adduser, network-manager (>= 1.2),
Running openconnect on the command-line, the environment variables are
all present.
echo $COOKIE | /usr/sbin/openconnect --interface vpn0 mydomain.com
--cookie-on-stdin
---
CISCO_CSTP_OPTIONS=X-CSTP-Version=1
CISCO_DEF_DOMAIN=mydomain.com
CISCO_SPLIT_EXC_0_ADDR=0.0.0.0
Currently I'm having to work around by putting in a wrapper script
instead of nm-openconnect-service-openconnect-helper.
#!/bin/bash
# Routes that we want to be used by the VPN link
ROUTES="10.0.0.0/8 \
10.96.52.0/22 \
10.96.16.111/32 \
..."
# Helpers to create dotted-quad
Public bug reported:
When connecting to an openconnect VPN using network-manager-gnome, non
of the CISCO_SPLIT_INC environment variables are being exported to the
helper program.
To test:
dpkg-divert --add --rename --divert \
Public bug reported:
After applying fix for #1809452, #1819254 and #1819258.
---
[CPU:0.0%|MEM:28.8%] ... 12:37:59,469 [asyncio
:1274][ERROR ] Future exception was never
retrieved
future:
Traceback (most recent call last):
This is the patch required to backport.
https://github.com/saltstack/salt/pull/47462
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819258
Title:
[FTBFS] salt: Could not import extension youtube
Public bug reported:
---
/usr/share/sphinx/scripts/python3/sphinx-build -b html -d _build/doctrees.
_build/html
Running Sphinx v1.7.9
loading translations [en]... done
Extension error:
Could not import extension youtube (exception: cannot import name 'Directive')
make[2]: *** [Makefile:72:
This is the patch required to backport.
https://github.com/saltstack/salt/pull/48705
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819254
Title:
salt-ssh: SyntaxError: invalid syntax
To manage
Public bug reported:
---
Setting up salt-common (2017.7.4+dfsg1-1) ...
File "/usr/lib/python3/dist-packages/salt/client/mixins.py", line 495
def async(self, fun, low, user='UNKNOWN', pub=None):
^
SyntaxError: invalid syntax
File
Having built and installed upstream packages
(http://repo.saltstack.com/py3/ubuntu/18.04/amd64/latest/)
With the following changes.
---
diff -pur salt_2018.3.3+ds.orig/debian/control salt_2018.3.3+ds/debian/control
--- salt_2018.3.3+ds.orig/debian/control2018-05-30 21:24:18.0
One possible cause might be the tornado package itself.
Upstream salt has the following dependency requirements.
---
tornado>=4.2.1,<6.0; python_version < '3'
tornado>=4.2.1,<5.0; python_version >= '3.4'
---
However the tornado package maintainer pushed the untested/unsupported version
Public bug reported:
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910236
As per Debian bug, importing the module directly / running the
problematic code in python interpreter works fine.
On debugging, I found another error reproducible with the following:
---
>>> import ssl
>>>
Looks like they moved repo to github. New links.
First bad commit (causes this bug).
https://github.com/GNOME/meld/commit/07ec4fd9b01d8efdf74cc268dc35aa4f5791c48b
#diff-0cf74878a4eeb2f48ed581806c8922a8
Patch that fixes bug.
** Changed in: xchat (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/647633
Title:
xchat doesn't wait for authentication to succeed before
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666260
Title:
"Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
To manage notifications about this bug
As original poster, if I didn't continue to post oom dumps, perhaps
things started to peter out on 4.8.0-39 or later.
What was particular about the load that triggered this bug was heavy IO
putting cache pressure on ext4 on a system where there's zero locality
of reference in anything read from
Servers are now running on 4.10 kernels, so I guess no one cares about
4.8 anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666260
Title:
"Out of memory" errors after upgrade to 4.4.0-59 +
Thanks.
By the way, also confirming that the patch works here (have been running
the patched kernel for 3 days now). Running on hardware Super Micro
X9SCL with an Intel 82574L NIC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Meld version 3.18.0 in arty has a really bad memory problem that didn't
happen in 3.16.4.
Git bisect says that this is the first bad commit.
https://gitlab.gnome.org/GNOME/meld/commit/07ec4fd9b01d8efdf74cc268dc35aa4f5791c48b
And this patch applied to master 3 weeks ago
Hi, will these patches also land in the HWE kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730550
Title:
e1000e in 4.4.0-97-generic breaks 82574L under heavy load.
To manage notifications
Public bug reported:
First traceback looks to be the cause. The second traceback is the
effect that followed (repeatedly).
Don't think it's specific to system76.
Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here
]
Apr 30 09:56:10 galago kernel: [97085.090137]
Another 4 servers OOM'd on 4.8.0-36 over the weekend. Upgraded to
4.8.0-39
** Attachment added: "linux-48036.oom4.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827637/+files/linux-48036.oom4.txt
--
You received this bug notification because you are a member
** Attachment added: "linux-48036.oom7.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827641/+files/linux-48036.oom7.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "linux-48036.oom5.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827639/+files/linux-48036.oom5.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "linux-48036.oom6.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827640/+files/linux-48036.oom6.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And again on 4.8.0-36. Upgraded server to 4.8.0-39. (How many times must
I keep on doing this?)
** Attachment added: "linux-48036.oom3.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4825946/+files/linux-48036.oom3.txt
--
You received this bug notification
And again on 4.8.0-36. Upgraded server to 4.8.0-39.
** Attachment added: "linux-48036.oom2.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4825131/+files/linux-48036.oom2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
Same as #1655842 - Started seeing oom-killer on multiple servers
upgraded to 4.4.0-59.
Unlike #1655842, also seeing the same oom-killer on multiple servers
updated to 4.8.0-34.
First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
No OOM on servers running 4.4.0-63 just yet, but the memory usage on
them is weird to say the least. The Buffer/SLAB ratio is completely
different from 4.4.0-57.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And 4.8.0-36 is affected by bug also.
** Attachment added: "linux-48036.oom.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4823499/+files/linux-48036.oom.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attaching current slabtop
---
# cat /proc/meminfo
MemTotal: 32856000 kB
MemFree: 381632 kB
MemAvailable: 30990804 kB
Buffers:28709688 kB
Cached: 221664 kB
SwapCached: 184 kB
Active: 24854232 kB
Inactive:5393552 kB
Active(anon):
SLAB is still dropping.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666260
Title:
"Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
To manage notifications about this bug go to:
I think this is currently in the middle of happening right now on one of
the servers running 4.4.0-63.
SReclaimable is down from 15GB to 5GB, and Buffers is has been slowly
rising over the last hour from 12GB to approaching 25GB.
---
# cat /proc/meminfo
MemTotal: 32856000 kB
MemFree:
Attaching the call trace for 4.4.0-59, this is from Jan 16th.
** Attachment added: "linux-44059.oom.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822833/+files/linux-44059.oom.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attaching the call trace for 4.8.0-34, this is from Feb 19th.
** Attachment added: "linux-48034.oom.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822834/+files/linux-48034.oom.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Same as #1655842 - Started seeing oom-killer on multiple servers
upgraded to 4.4.0-59.
Unlike #1655842, also seeing the same oom-killer on multiple servers
updated to 4.8.0-34.
First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
4.4.0-63. I am seeing no
The OOM fixes were introduced in 4.4.0-58 according to the changelog,
but sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To
This is the reported /proc/meminfo Buffers usage for 4 different kernel
versions. We got the same OOM call traces on both 4.4.0-58 and
4.8.0-34, I highly doubt that to be a coincidence.
** Attachment added: "meminfo-buffers.png"
Yes they are, I'm seeing the same exorbitant memory usage that we had on
4.4.0-58 as am currently getting on 4.8.0-36.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory"
Bug is prevalent on 4.8 kernels too.
---
[251529.693133] CPU: 3 PID: 1547 Comm: icinga2 Not tainted 4.8.0-34-generic
#36~16.04.1-Ubuntu
[251529.693134] Hardware name: MSI MS-7823/B85M-G43 (MS-7823), BIOS V3.14B3
06/23/2014
[251529.693135] 0286 e9fa7ede 95c3f774bb38
Applied upstream: https://github.com/D-Programming-
GDC/GDC/commit/96b60cbd066c856b37d9b4b5f5514d6314324a3e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620681
Title:
ICE when building
There's a small circle going on. Initial semantic analysis has
completed, and compiler is now lowering to gcc, however certain spots
may encounter symbols that haven't been analysed (won't be emitted, but
benefits debugging if we pass their complete symbol information to gcc).
And so it stops to
Thanks, I also reported here just for completeness sake:
https://bugzilla.gdcproject.org/show_bug.cgi?id=239
Looking at the minimal test now...
** Bug watch added: bugzilla.gdcproject.org/ #239
https://bugzilla.gdcproject.org/show_bug.cgi?id=239
--
You received this bug notification because
Public bug reported:
In Ubuntu Precise (12.04) LTS ChangeLog (went out as part of 10.10 it
seems):
---
screen (4.0.3-14ubuntu2) maverick; urgency=low
* debian/screen-cleanup.upstart, debian/init: convert screen to an
upstart script to fix some bugs where /var/run is not mounted when
Hi Christopher, sorry for the delay, but I ended up ditching the
netbook, switching to a System76 laptop. It eventually reached the
point where I needed something more powerful to work on.
I can certainly try booting the machine again and loading on 15.04, but
that will take some time.
--
You
Public bug reported:
In Ubuntu Precise (12.04) LTS ChangeLog (went out as part of 10.10 it
seems):
---
screen (4.0.3-14ubuntu2) maverick; urgency=low
* debian/screen-cleanup.upstart, debian/init: convert screen to an
upstart script to fix some bugs where /var/run is not mounted when
I don't think I've really been able to reproduce such a crash since
12.04 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708366
Title:
meld crashed with IndexError in checkpoint(): list
Current version is 0.6.7 in trusty.
Guess this can be closed.
** Changed in: cgdb (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014762
Title:
D
Public bug reported:
Screen locks up under certain scenarios.
May be a red herring but mostly seems to occur:
- Running a cpu or memory intensive process (Have 3.5GB RAM, 3.5GB Swap
on SSD. Freezes occur even when swap not in use, also has occurred
within minutes of booting up)
- Shortly
Public bug reported:
A test file:
---
#include stdio.h
int main()
{
long double a = 0x1.29aeffefc8ec645p+12557L;
printf(%Lf\n, a);
}
Whilst in gdb (on 32bit):
---
(gdb) p 0x1.29aeffefc8ec645p+12557L
$1 = 12558.16282653431
(gdb) p a
$2 = 1.2565231254743496882989195724989633e+3780
---
Do
This patch against libnss fixes the issue.
https://bugzilla.redhat.com/attachment.cgi?id=551038
Has this managed to find it's way into Debian/Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please consider adding this commit as an added patch to the cgdb 0.6.6
package from upstream cgdb.
http://cgdb.git.sourceforge.net/git/gitweb.cgi?p=cgdb/cgdb;a=commit;h=31b310915667b2ee529e93bcfabf1182404b8efe
Thanks
Iain
** Affects: cgdb (Ubuntu)
Importance:
No problem. I will try that.
Out of my own curiosity, what is usually the driver/module that controls
this? Will be eager to see if I can fix this myself.
Regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm is fixed in upstream kernel v3.2-rc2... just a shame about
the missing bcm wireless and fglrx drivers. ;-)
Regards.
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream-v3.2-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Installed Ubuntu 11.10 on HP Pavilion dm1. LED light on the Mute (F11)
key stays constant amber. It should alternate between colours when
pressed. Either amber/white, off/white, or off/amber.
Regards
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896873
Title:
Mute key LED light stays constant amber
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 798135 ***
https://bugs.launchpad.net/bugs/798135
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #798135, so it is being marked as such. Please look
Sounds similar, Christopher. Though there is not enough detail in your
description to be certain.
Does the workaround I posted fix your issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798135
*** This bug is a duplicate of bug 798135 ***
https://bugs.launchpad.net/bugs/798135
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #798135, so it is being marked as such. Please look
Made patch for the renamed menu file here:
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/798135/comments/12
I could rebuild the package and submit the diff.gz for uploading into Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah, looks like issue has been resolved in gnome-menus.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/gnome-
menus/oneiric/revision/111
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, thanks your your sudden enthusiasm of my report. I wrote the script
somewhat 2 years ago now as a proof of concept, and I've never had the
need for spell checking feature in command-not-found. :~)
I will see what I can do to help, though I am a bit stretched for time
these days.
Regards.
*** This bug is a duplicate of bug 798135 ***
https://bugs.launchpad.net/bugs/798135
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #798135, so it is being marked as such. Please look
Workaround:
sudo ln -s gnome-applications.menu /etc/xdg/menus/applications.menu
Patch:
--- a/src/shell-app-system.c
+++ b/src/shell-app-system.c
@@ -199,7 +199,7 @@
* handle NODISPLAY semantics at a higher level or investigate them
* case by case.
*/
- priv-apps_tree =
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798135
Title:
gnome-shell crashed with signal 5 in shell_app_system_get_sections()
To manage notifications about this bug go to:
The fact that the applications menu has been renamed to 'gnome-
applications.menu' seems ubuntu and/or debian-specific to me. So my
guess is no.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798135
http://changelogs.ubuntu.com/changelogs/pool/main/g/gnome-menus/gnome-
menus_3.0.1-0ubuntu4/changelog
See changelog for gnome-menus (3.0.0-0ubuntu1) oneiric; urgency=low:
* debian/patches/06_menus_rename.patch:
- Rename applications.menu to gnome-applications.menu
Regards
--
You
Thank you for taking the time to make Ubuntu better. I cannot reproduce
this on my machine, could you perhaps provide more details on what you
do / how you've obtained the applications you're using? (Just noting
that deadbeef doesn't seem to be in the repositories)
** Changed in: fluxbox
On the note of the attention notification and it's behaviour - was this the
commit that actually added that blue arrow?
http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/1096
I became rather fond of the Ubuntu logo lighting up blue, and wondered if you
could add it as an optional
I've been a bit busy lately to put a package together (though there is
one for testing in my PPA) - I would have thought that by now the
package window would be closed by now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, using upstream sources (I am developing the D frontend language to
work with GCC-4.6). I take it that there are no multiarch patches
available yet for 4.6? Debian experimental maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: binutils
Recent update in natty (something multiarch-related) and all my local
gcc builds can no longer link any executables.
/usr/bin/ld: cannot find crti.o: No such file or directory
/usr/bin/ld: cannot find -lc
/usr/bin/ld: cannot find crtn.o: No
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738098
Title:
ld: cannot find crti.o: No such file or directory
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*WORKAROUND*
LIBRARY_PATH=/usr/lib/i386-linux-gnu:$LIBRARY_PATH
export LIBRARY_PATH
That in your .bashrc file (or ran from a console) is enough for GCC to find the
new location of library/ctor/dtor files.
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs,
May have to move this over to GCC, as it actually looks to be the role
of the compiler to find crti.o, crtn.o, etc. Not the linker...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738098
Title:
ld:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708366
Title:
meld crashed with IndexError in checkpoint(): list index out of range
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: unity
Raising bug against Unity until I know more about it. But essentially
there is an area of the screen which is inaccessible to the cursor from
clicking actions. Which can get rather disrupting when a lot of your
activity seems to reside in that
** Attachment added: Screenshot-7.png
https://bugs.launchpad.net/bugs/706680/+attachment/1804203/+files/Screenshot-7.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706680
Title:
Cannot
For clarification, the area coloured black is a visual representation,
and not what I can actually see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706680
Title:
Cannot click in small square area
Attaching patch, can someone review/upload?
Can't use meld to compare two directories without this.
Regards
** Patch added: natty-python.patch
https://bugs.launchpad.net/ubuntu/+source/meld/+bug/703603/+attachment/1797692/+files/natty-python.patch
--
You received this bug notification
** Changed in: meld (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703603
Title:
TypeError: value is of the wrong type for this column
--
ubuntu-bugs
Public bug reported:
Binary package hint: meld
Backtrace:
Traceback (most recent call last):
File /usr/bin/meld, line 123, in module
main()
File /usr/bin/meld, line 116, in main
app.parse_args(sys.argv[1:])
File /usr/lib/meld/meld/meldapp.py, line 621, in parse_args
tab =
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703603
Title:
TypeError: value is of the wrong type for this column
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The only notably change to my system since meld stopped working seems to
be python-minimal from 2.7.1-0ubuntu4 to 2.7.1-0ubuntu5
Think it's too late to downgrade it though just to be sure...
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Lazy fix:
diff -ur /usr/lib/meld/meld.orig/tree.py /usr/lib/meld/meld/tree.py
--- /usr/lib/meld/meld.orig/tree.py 2010-12-13 16:15:35.0 +
+++ /usr/lib/meld/meld/tree.py 2011-01-16 17:05:25.212220421 +
@@ -109,7 +109,7 @@
STATE = self.column_index(COL_STATE, pane)
More lazy fixes (now loads and functions as I expect for now):
diff -ur /usr/lib/meld/meld.orig/tree.py /usr/lib/meld/meld/tree.py
--- /usr/lib/meld/meld.orig/tree.py 2010-12-13 16:15:35.0 +
+++ /usr/lib/meld/meld/tree.py 2011-01-16 17:22:40.936220421 +
@@ -84,8 +84,8 @@
Can confirm someone else getting this too using a Logitech USB headset.
Uninstalling linux-backports-modules-alsa-lucid-generic indeed does
resolve the nasty bit of the issue. However, am unable to use the
headset in any applications after applying the workaround.
Pastebin'd logs:
Public bug reported:
Binary package hint: xchat
xchat doesn't wait for authentication to succeed before autojoining
channels, so I cannot autojoin any of the invite-only channels I'm part
of.
Problem not seen in Lucid, however it may interest you that this issue
is also present on Lucid booting
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/647633/+attachment/1635634/+files/Dependencies.txt
--
xchat doesn't wait for authentication to succeed before autojoining channels
https://bugs.launchpad.net/bugs/647633
You received this bug notification because you are
** Description changed:
Binary package hint: xchat
xchat doesn't wait for authentication to succeed before autojoining
channels, so I cannot autojoin any of the invite-only channels I'm part
of.
+
+ Problem not seen in Lucid, however it may interest you that this issue
+ is also
In mine, super + alt
--
unity crashes if a place is opened with the super-short-key
https://bugs.launchpad.net/bugs/632460
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Adding debug session of running unity (via mutter).
Any more info needed, just ask. Regards.
** Attachment added: gdb session running unity
https://bugs.launchpad.net/unity/+bug/632460/+attachment/1579203/+files/unity-session.txt
--
unity crashes if a place is opened with the
Function:
private void on_super_key_modifier_release (uint keycode)
{
if (!Unity.global_shell.super_key_active) return;
int index = (int)keycode - 10;
index = int.min (index, model.size - 1);
if (index 0 || index 9) return;
Unity.global_shell.super_key_active = false;
var
bug #549782 is fixed, so should be this bug I guess...
** Changed in: nitrogen (Ubuntu)
Status: Confirmed = Fix Released
--
nitrogen crashed with SIGSEGV at startup when restoring wallpaper
https://bugs.launchpad.net/bugs/520861
You received this bug notification because you are a member
This got fixed a while ago. Closing.
** Changed in: gdc-4.3 (Ubuntu)
Status: Confirmed = Fix Released
--
Classes nested in functions are not written to object files
https://bugs.launchpad.net/bugs/570913
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: command-not-found
Considering command-not-found has a relatively simple job. It seems that
it is horribly over-engineered for its task. And as such, we have
runtimes such as this:
$ time sl
The program 'sl' is currently not installed. You can install
1 - 100 of 109 matches
Mail list logo
