@rbalint Should this bug be reopened until the fix actually gets merged?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803808
Title:
wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
T
Fixed in v2.6.10rc0-40-g000cc11d8f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803808
Title:
wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
To manage notifications about this bug
According to https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13594 this has
been fixed in:
v2.9.0rc0-1153-g536e26c55e
v2.6.2rc0-130-gc1fb20adc7
As long as people enable the security or -updates repo, they should have
at least Wireshark 2.6.8 which has this fix incorporated.
** Bug watch adde
*** Bug 15894 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803808
Title:
wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
To manage no
As reported in https://bugs.launchpad.net/ubuntu/+bug/1803808, the issue
cannot be reproduced on 3.0, but only 2.6. Bisection led up to:
3a0da5fbb2c907eb9070127aefd1a8e2415c is the first bad commit
commit 3a0da5fbb2c907eb9070127aefd1a8e2415c
Date: Mon Jul 16 09:06:39 2018 -0700
Qt:
This appears to be fixed in Wireshark 2.4.6 and newer.
** Changed in: wireshark (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/1759512
Title:
capture from
Hi, can you still reproduce this issue? If so, what package and distro
version? You can use this command to find out:
apt-cache policy wireshark-qt
To obtain a trace, use:
gdb -q -ex r wireshark
Once it crashes, use the "bt" command (without quotes) to obtain a
backtrace.
** Changed in
libwireshark8 being half-installed is rather strange. If the original
reporter does not provide more details (such as further terminal
output), I'd suggest to close this issue.
** Changed in: wireshark (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you ar
** Changed in: wireshark (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/1463673
Title:
Wireshark's UI is unusable in Ubuntu 15.04 with Gnome3
To man
As Balint noted, this is likely an issue with the Qt installation. There
have been many improvements in newer Qt versions, so upgrading to Ubuntu
16.04 and newer should help.
** Changed in: wireshark (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a m
** Changed in: wireshark (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/1282805
Title:
Wireshark repository URL changed
To manage notifications abou
** Changed in: wireshark (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413609
Title:
Wireshark does not refresh the UI correctly
To manage notifications abou
** Changed in: wireshark (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/1243555
Title:
Wireshark crashes with a SIGSEGV when starting a capture or opening
** Changed in: wireshark (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/767267
Title:
X.509 vulnerability in Wireshark version 1.2.0 to 1.2.15
To ma
*** This bug is a duplicate of bug 1803808 ***
https://bugs.launchpad.net/bugs/1803808
** This bug has been marked a duplicate of bug 1803808
wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Oops, the commit reference for the master-2.6 branch was wrong, I meant to say:
* master-2.6 v2.6.8rc0-23-ga616bd2
I have completed bisection and will propose a patch upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Can reproduce the crash with a fully up-to-date Ubuntu 16.04.
libqt5gui5:amd64 5.5.1+dfsg-16ubuntu7.6
wireshark-qt 2.6.8-1~ubuntu16.04.0
(gdb) bt
#0 QIconPrivate::~QIconPrivate (this=0x580aaf60, __in_chrg=) at image/qicon_p.h:64
#1 QIcon::~QIcon (this=, __in_chrg=) at
image/qicon.cpp:681
#
The commit that Mikael refers to links to bug 14979.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803808
Title:
wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
To manage notificatio
See also the comments in
https://unix.stackexchange.com/questions/106614/preseed-cfg-ignoring-hostname-setting,
and in particular the reference to
http://d-i.alioth.debian.org/manual/en.i386/apbs04.html#preseed-network
The hostname is probably a very common case though.
I am currently using thi
There are two problems with the patch:
1. netcfg/hostname=ubuntu (or any value containing "ubuntu") remains unfixed.
2. Certain DHCP hostnames can result in corrupting the hosts file.
For example, with DHCP name "node" and "netcfg/hostname=newname" we have this
command:
/bin/sed -i "s/$CURRENT_HO
The TypeError is fixed by commit
9a6cdd9cee773b5b315aef81d32f629c48760e5c upstream. Though at this point,
I would recommend just taking a git snapshot from master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Same problem with exiting Wireshark (wireshark-qt). Would a SRU be possible
with this change:
https://quickgit.kde.org/?p=breeze.git&a=commit&h=9b3d268f5f36ce7a635875223469bc4e8e2b3542
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This (upstream) patch was merged into Breeze v5.8 but applies cleanly on
v5.5.5 (in the repos).
** Patch added: "[PATCH] Fix crash on exit"
https://bugs.launchpad.net/ubuntu/+source/breeze/+bug/1545783/+attachment/4777312/+files/0001-Fix-crash-on-exit.patch
--
You received this bug notificat
I doubt that the package will be updated for things other than security
updates.
A Debian/Wireshark developer maintains more recent packages in a PPA, please
give it a go:
https://launchpad.net/~wireshark-dev/+archive/ubuntu/stable
--
You received this bug notification because you are a member
HP ZBook Studio G3 (i7-6700HQ/Quadro M1000M)
BIOS N82 Ver. 01.07, 04/27/2016)
Workaround to avoid lockup issue with nouveau/bbswitch, add this to cmdline:
acpi_osi=! acpi_osi="Windows 2009"
https://github.com/Bumblebee-
Project/Bumblebee/issues/764#issuecomment-234494238
** Attachment added: "HP
These issues are harmless, the Nvidia driver and firmware writes are
non-compliant against the ACPI specification and implemented the wrong
type, but if the standard would be enforced, then it would break stuff.
** Changed in: acpi (Ubuntu)
Status: Confirmed => Invalid
** Changed in: bumbl
Yuri, please do not add the whole hybrid-graphic-linux mailing list, it
might be a bit noisy.
The error from comment 6 is the same as in
https://bugs.freedesktop.org/show_bug.cgi?id=93460, though under
different circumstances.
The amdgpu driver is under development by AMD and your hardware is qui
@Dewald You have the same issue as MSI GE62 6QD Apache Pro (and in a
different way, the the Clevo P651RA/P651RE/... models). A workaround
(based on an analysis of ssdt6.dsl) is to boot with:
acpi_osi=! acpi_osi="Windows 2009"
This will make the firmware use a method for Windows 7 which does n
Clevo N155RF (BIOS 1.05.02RLS1 01/04/2016).
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530
[8086:191b] (rev 06) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206M [GeForce
GTX 965M] [10de:1427] (rev ff) (prog-if ff)
Obt
Your disk seems broken. Have you checked the disk health?
smartctl -a /dev/sda
** Changed in: bbswitch (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532538
Something broke in the past and affected the current installation.
Please try these commands in order to remove the bbswitch module and
continue the installation through apt:
sudo dkms remove -m dkms -v 0.7 --all
sudo apt-get install -f
Now you should see bbswitch when running this comman
In June 2015 there was another attempt to get this patch merged[0], it
seems that people are now recommending/leaning towards replacing xf86
-video-dummy[1] by Xvfb[2][3].
The patch looks trivial enough to get merged, but maybe it never will
due to Xvfb deprecation (=WONTFIX)?
[0]: http://patchw
Fixed in Ubuntu 15.04 Vivid. Ubuntu 14.04 Trusty is not fixed though.
** Changed in: upower (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/1437377
Title:
As reported on several places, UPower fails to recognize Unifying
devices after an update to kernel >= 3.19. This includes Vivid.
Please try the attached patch on /lib/udev/rules.d/95-upower-csr.rules
(commit f8104a112eb967cd4c2aaf57b5a59aafe7c4738f upstream).
** Patch added: "[PATCH] rules: supp
Do you have a full dmesg since the first boot? I have seen machines
having issues due to hotplugging where the device is gone during
suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318040
Titl
This problem may occur when your compiler (gcc) is different than the
one used to compile the kernel. Have you installed an older gcc version
(maybe via CUDA?). What does `gcc -v` show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
If you install a mainline kernel, then you must install the
corresponding kernel header packages as well. Not a bug in bbswitch.
** Changed in: bbswitch (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Chunkin has been replaced by the chunked module which is enabled by
default. This is present since nginx 1.3.9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438440
Title:
nginx-extras does not inc
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438440
Title:
nginx-extras does not include Chunkin module
To manage notifications about t
The default params are load_state=-1 unload_state=-1 ("do not change").
bumblebeed will write OFF to /proc/acpi/bbswitch which has no effect if
it was already off. So it does not matter what values you use for
load_state, the end result will be comparable to load_state=0.
On stop, bumblebeed does
You can have both bumblebee and nvidia-prime installed. Even nouveau +
PRIME would work, it just requires appriopriate configuration. This
could be useful for experimenting or if you want to use
bumblebeed/bbswitch to save power and to use nvidia-prime at other times
(requires restarting X though).
"3.18.3-031803-generic"
This looks like a mainline kernel from the Ubuntu Kernel PPA. Either
uninstall it and revert to the stock kernel or install the apprioriate
linux-headers-3.18... headers package.
** Changed in: bbswitch (Ubuntu)
Status: New => Invalid
--
You received this bug noti
This could have something to do with Energy Efficient Ethernet (802.3az).
http://permalink.gmane.org/gmane.linux.network/197197
I also experience a situation on the mainline kernel where no link is
detected upon plugging in the cable.
--
You received this bug notification because you are a membe
Even ECDHE-RSA-AES128-SHA (TLSv1.0) did not work, it turns out that
another change is needed for ECDHE suites. Please consider applying this
one too, it is more CPU friendly.
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=3164721462d547fa2d15e2a2f07eb086a3590fd5;hp=91484409bdd17
Public bug reported:
While the PostgresQL server supports versions higher than TLS 1.0, this
is not enabled in libpq:
src/backend/libpq/be-secure.c:738: SSL_context =
SSL_CTX_new(SSLv23_method());
src/interfaces/libpq/fe-secure.c:969: SSL_context =
SSL_CTX_new(TLSv1_metho
FYI, this bug is fixed upstream.
Debian has applied a single patch[0] that takes care of the greatest
offender, upstream has more fixes[1] that plugs the remaining leaks.
[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766762
[1]: https://bugs.freedesktop.org/show_bug.cgi?id=82659
** Bu
Correct bug link (what does UPower have to do with LO :/)
https://bugs.freedesktop.org/show_bug.cgi?id=82659
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757551
Title:
upowerd leaks memory with Log
Possibly a related bug:
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=82659
** Bug watch added: LibreOffice Bugzilla #82659
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=82659
** Bug watch added: freedesktop.org Bugzilla #82659
https://bugs.freedesktop.org/show_bug.cgi?id=8265
UPower 0.99.1 had one minor fix which fixed a memleak:
dbb9bead6d3b9e70a5d58019b1615d2a6fba5312
Another leak fix:
b1aeed994884602b3601a7f4b98419c65be9009c
I am working to flesh out more memory leaks here:
https://git.lekensteyn.nl/upower/log/?h=memleak-fixes
The GetStatistics calls are probably
Not sure why this was posted on the devkit-devel list. Anyway, please
attach the backtrace of urfkilld when the buggy condition is triggered:
sudo gdb -q -batch -ex bt -p $(pidof -s urfkilld)
Hopefully it will actually contain useful information, otherwise you
need to rebuild the package with
I am with Vincent-C here, primus (primus-libs) is a better package to
attach the dependency on.
** Also affects: primus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: primus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a mem
The bbswitch init script is only recommended if you do not use bumblebee
with bumblebeed.
Otherwise, I suggest to set `TurnCardOffAtExit=false` in
/etc/bumblebee/bumblebee.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: bbswitch (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357663
Title:
bbswitch-dkms 0.7-2ubuntu0.0.1: bbswitch kernel module failed to build
Could not reproduce with Kubuntu 14.04.1 32-bit (Live CD without and
with updated kernel packages). Ensure that you have linux-headers-
generic installed and do not use non-standard compilers in the default
path.
** Changed in: bbswitch (Ubuntu)
Status: New => Incomplete
--
You received t
I can't read Russian, please run the command with an English locale:
sudo LC_ALL=C dkms autoinstall
I guess that you have not installed kernel headers matching your kernel.
Please check that first.
** Changed in: bbswitch (Ubuntu)
Status: Confirmed => Incomplete
--
You received this
Hi Tye,
On Monday 01 September 2014 02:37:43 Tye wrote:
> I'm using Sony VAIO VPCZ135GW.
> I realized that bbswitch failed to be manipulated on my machine, and it also
> blocked the way to suspend, hibernate
>
> root@tye-VPCZ135GW:~# cat /proc/acpi/bbswitch
> Segmentation fault
This (and the
Have you enabled some special CFLAGS somewhere?
Could you try to remove the non-standard GCC packages you have on your
system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357663
Title:
bbswitch-
bbswitch load_state=-1
lspci -nnvvd10de:
sudo tee /proc/acpi/bbswitch << Incomplete
** Changed in: bbswitch (Ubuntu)
Assignee: (unassigned) => Peter Wu (lekensteyn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
This is not a bbswitch bug (see also comment 2), but in the Ubuntu
kernel packaging. Please try a newer kernel, 3.13.0-24 seems to have
fixed this.
Related:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1311121/comments/3
** Changed in: bbswitch (Ubuntu)
Status: Confirmed => Inva
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: b
60 matches
Mail list logo
