You might want to file bugs for the other packages too:
# apt-cache rdepends libgtk2.0 | wc -l
1390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758210
Title:
Please remove hexchat from Ubuntu
T
Hi, pidgin dev here, got a report from an ubuntu artful user that it
generated a bunch of zombie processes.
I noticed a patch named "hg-remove-SIGCHLD-handler.patch" that only
exists in ubuntu and not in debian, and seems to be a backport of
https://bitbucket.org/pidgin/main/commits/161320946afdd6
I noticed someone else filed an "Intent to file removal bug" in debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891982
** Bug watch added: Debian Bug tracker #891982
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891982
--
You received this bug notification because you are a mem
Public bug reported:
The xchat package was removed from debian on 2016-01-30[1]. The
mentioned reason is "dead upstream; active fork available". It hasn't
had a stable release in 8 years, and it's been replaced by hexchat,
which is still actively developed.
All other distros have removed the xcha
This is equivalent to https://bugzilla.gnome.org/show_bug.cgi?id=648419
The backtrace of that bug shows remove_capslock_feedback() instead of
keymap_state_changed() because remove_capslock_feedback() is tail-called
from keymap_state_changed(). The crash is essentially the same (priv
being null), t
Wouldn't that mean that gnutls28 and openssl are vulnerable, then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553819
Title:
Regression in trusty's gnutls26, can't connect to servers with RSA-MD5
Public bug reported:
Ubuntu version: 14.04
Affected package versions:
- 2.12.23-12ubuntu2.4
- 2.12.23-12ubuntu2.5
Unaffected package versions:
- 2.12.23-12ubuntu2.3 and older
Description:
When trying to connect to servers that have a RSA-MD5 signature in their
certificate chain, gnutls26 fail
Okay got my dev pc back and tested this.
The test case in the description is passing with the wily-proposed
package, 2.10.11-0ubuntu4.1
Had to adjust the fd limit i originally suggested for the test to be
more reliable - 20 was a bit too low and was sometimes failing during
startup even, so I use
Sorry for the delay testing this, just got my dev pc back.
Both test cases from the description are passing with the wily-proposed
packages, version 1.6.3-1ubuntu1
Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you ar
I haven't had access to my dev computer for a few weeks so I couldn't
test that wily-proposed package yet. I would appreciate if someone else
did - the test case in the description is fairly easy to set up, IMO.
However, note that bug #1529445 is not the same thing as this bug - the
wily-proposed
That's how bugs work here. They start as something for development
versions only and then they are nominated to be fixed in stable
releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479715
Title
*** This bug is a duplicate of bug 1479715 ***
https://bugs.launchpad.net/bugs/1479715
** This bug has been marked a duplicate of bug 1479715
Crash due to fd leak when playing sounds in pidgin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Created bug 1529445, which is about a different fd leak in gstreamer
1.6.0 itself that can result in the exact same crash in pidgin as this
bug.
It's not as straightforward as this bug in that it doesn't leak
constantly for all users, but requires, for example, not having a sound
card or some othe
Public bug reported:
Ubuntu 15.10 includes gstreamer 1.6.0. There were several important leak
fixes in 1.6.1, some of which also meant holding references to file
descriptors around, which can result in crashes once the fd limit is
hit.
Upstream bugs:
https://bugzilla.gnome.org/show_bug.cgi?id=75
Fix from https://hg.pidgin.im/pidgin/main/rev/902b1fd334bd
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding pidgin. This problem was most recently seen with version
1:2.10.11-0ubuntu4, the problem page at
https://errors.ubuntu.com/prob
Thanks to everyone who helped <3
Really happy to finally be able to consider this completely solved :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315550
Title:
Current 14.04 bitlbee build using
Got 3.2.1+otr4-1ubuntu0.2, all four tests passing. Everything else seems
to be working normally too.
...Is this enough for a SRU verification? Do I just go ahead and change
tags now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
>You need to have an upstream tarball (named e.g. bitlbee_3.4.1.orig.tar.gz)
>available in the parent directory.
>The 1.0 format falls back to a "native" package if it can't find the upstream
>tarball, which is probably not what you want.
Uh, well, I don't know what to do with this information.
There's this pending pull request, which i have no idea what to do with:
https://github.com/bitlbee/bitlbee/pull/43
It changes the format from "1.0" to "3.0 (quilt)" and by doing so it
breaks the build (it's got a red X from the travis-ci build).
Specifically, dpkg-buildpackage throws:
>dpkg-sou
Huge success! All four test cases in the ticket description are now
passing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315550
Title:
Current 14.04 bitlbee build using broken OTR (fixed in night
Nope! Same thing!
Here, have a command to check if the last part of that function changed:
# gdb -q -ex 'disas otr_filter_msg_out+240,+50' -ex q
/usr/lib/bitlbee/otr.so
Reading symbols from /usr/lib/bitlbee/otr.so...(no debugging symbols
found)...done.
Dump of assembler code from 0x479e to 0x47
3.2.1+otr4-1ubuntu0.1 still segfaults.
A disasm at the point of the segfault, near the end of
otr_filter_msg_out(), shows that it didn't change. The last few calls
are still otrl_message_sending() and g_free(), as opposed to g_strdup(),
otrl_message_free() and irc_usernotice()
Is this something r
Oh I should probably expand on the "what's going on": this is still very
broken in trusty (even though it says fix released - that's vivid) and
we still regularly get users complaining about it every few months. I
don't want to keep dealing with the issue for the next few years.
Please.
--
You re
02:07 < ScottK> If you know how to fix it, attach the patch to a bug, explain
what's going on and subscribe the ubuntu-sponsors team to the bug.
02:08 < ScottK> All the distro specific specific bureaucracy they should be
able to handle.
02:10 < dx> there are several bugs
Updated description to fit the SRU template, and I just noticed that
each description change shoots an email. Sorry for that!
** Description changed:
The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr
in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems
** Description changed:
The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr
in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems
in the OTR negotiation phase. These problems have been fixed in the
nightlies for bitlbee. Relevant tickets are:
htt
** Description changed:
The current version of bitlbee, bitlbee-common, and bitlbee-plugin-otr
in 14.04 is 3.2.1+otr4-1. In this version, there are numerous problems
in the OTR negotiation phase. These problems have been fixed in the
nightlies for bitlbee. Relevant tickets are:
htt
Oh thanks jelmer for appearing. #ubuntu-bugs didn't reply ;_;
So "fix released" is okay even if it's just the development version, and
the ticket is about trusty and utopic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
So apparently I can change the status of this issue to "fix released"
(in vivid)
** Changed in: bitlbee (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/
Wait. Dammit. Wrong status. Can't set it back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315550
Title:
Current 14.04 bitlbee build using broken OTR (fixed in nightlies)
To manage notifications
3.2.2-2 is in vivid now, arrived a bit too late for utopic :(
I'll be looking into what's needed to SRU this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315550
Title:
Current 14.04 bitlbee build
This is fixed in the 3.2.2 release, which introduces proper OTR support.
To summarize the issues found and fixed:
- crashing when sending messages to contacts with no previous otr context
- silently dropping all messages when opportunistic otr is enabled, which is
the default mode
- receiving a /
Thank you Apteryx. I had the same problem, and reverting to DHCP,
rebooting and setting same IP again solved problems with vino.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770477
Title:
[natty] C
I have the same problem, on Windows 7 OS, but IT'S NOT THE OS or THE
FIREFOX SOFTWARE FAULT.
IT'S MOUSE'S WHEEL FAULT!!! AAARGH!!!
I just figured out...
--
Firefox 3.5 (Shiretoko): middle-click on link opens _two_ tabs
https://bugs.launchpad.net/bugs/396252
You received this bug notification be
No solution on how i can restore missing
/apps/nautilus/list_view/default_visible_columns key and the others keys
i'm missing?
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs/246825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
i think that i have a corrupted gconf... because the only 2 childs of
/apps/nautilus in my config are "desktop" and "preferences"
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs/246825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
here i'm again... i hope this backtrace is useful
** Attachment added: "gdb-nautilus.txt"
http://launchpadlibrarian.net/16167043/gdb-nautilus.txt
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs/246825
You received this bug notification because you are a member of Ubuntu
Bu
damn... no... sorry!
I'll try to insert it this evening when i'm at home.
Sorry again.
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs/246825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
i have read gdb instruction better...
here is the gdb output
** Attachment added: "gdb-nautilus.txt"
http://launchpadlibrarian.net/16110670/gdb-nautilus.txt
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs/246825
You received this bug notification because you are a member
libeel2-2-dbgsym doesn't exist...
same error occurs if i change any directory to VIEW AS LIST instead of
VIEW AS DETAILS
thanks
** Attachment added: "gdb-nautilus.txt"
http://launchpadlibrarian.net/16120664/gdb-nautilus.txt
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs
Attached i capture with strace the problem
** Attachment added: "nautilus.txt"
http://launchpadlibrarian.net/16106272/nautilus.txt
--
nautilus restart entering folder
https://bugs.launchpad.net/bugs/246825
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I can't create a backtrace because gdb tells QUIT after the nautilus
start...
Anyways... again using tail -f .xsession-errors i see this:
** Eel:ERROR:(eel-preferences.c:673):update_auto_string_array: assertion
failed: (callback_data != NULL)
Initializing nautilus-share extension
seahorse nautil
Public bug reported:
Binary package hint: nautilus
Nautilus restart entering folder like .aMule in my home directory or a
folder inside a NTFS-3G mounted partition.
Error in .xsession-errors are:
**
** Eel:ERROR:(eel-preferences.c:673):update_auto_string_array: assertion
failed: (callback_data
*** This bug is a duplicate of bug 48679 ***
https://bugs.launchpad.net/bugs/48679
I got the same problem!
--
Birthday in Contacts is wrongly auto-adjusted +100 years
https://bugs.launchpad.net/bugs/78744
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
44 matches
Mail list logo
