** Attachment added: "DpkgTerminalLog.txt"
http://launchpadlibrarian.net/26319911/DpkgTerminalLog.txt
--
problem with kdelibs5-data on distribution upgrade
https://bugs.launchpad.net/bugs/371769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: kdelibs5
On upgrading to 9.04, this error occured:
E: /var/cache/apt/archives/kdelibs5-data_4%3a4.2.2-0ubuntu5_all.deb:
unable to stat `./usr/share/kde4/apps/kconf_update/kcookiescfg.upd'
(which I was about to install)
Reinstalling or Removing doesn't w
As I mentioned on the Arch Linux tracker, I think there are good reasons
for declaring an explicit dependency on tzdata even if it the dependency
should be satisfied transitively or implicitly:
https://bugs.archlinux.org/task/68642?project=1&string=python
Presumably it doesn't hurt anything to exp
Public bug reported:
PEP 615 added a compile-time option for specifying the location of time
zone data, with a primary use case being that it would allow distros to
specify where the system-deployed zoneinfo files are.
See https://www.python.org/dev/peps/pep-0615/#compile-time-options and
https:/
This is getting far too confusing because multiple patches for multiple
bugs are being conflated. I produced a fairly straightforward patch that
fixed an issue I directly saw in people's backtraces, and other issues I
identified that are similar. This is what this bug report is for.
The later patc
I also experienced the bug (13.10, Pidgin 2.10.7 (libpurple 2.10.7),
pidgin-otr 4.0.0-1). After doing some research I think I can conclude
that the reason must be that Pidgin tries to get the initialization
randomness from /dev/random and stalls until /dev/random delivers
sufficient data.
For me p
This bug was fixed in version 2.3. Current version of dateutil is 2.4.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438242
Title:
parse() on an invalid time string no longer raises ValueError
To
Public bug reported:
Discord and several other applications using libappindicator are widely
reported to have been crashing for several years. See:
https://github.com/flathub/com.discordapp.Discord/issues/30 (and others)
This is the backtrace:
(gdb) bt full
#0 0x7fe1d5d2e00e in () at /app/l
So, the patch is wrong. It fixes *a* bug, but not *the* bug. There
appear to be multiple g_signal_emit calls that don't match the
definition of the g_signals they're emitting. See:
https://bugs.archlinux.org/task/65885
Unless I'm missing something, they all need to be fixed. I will audit
them all,
I've gone through the code and cleaned up all g_signal_emit and
g_signal_new calls so they correspond with each other and make sense. No
external API changes. Wrote up a simple test program to exercise the
basic functionality, and used things like blueman-tray to confirm other
edge functionality wo
10 matches
Mail list logo
