*** This bug is a duplicate of bug 1898904 ***
https://bugs.launchpad.net/bugs/1898904
** This bug has been marked a duplicate of bug 1898904
Calibre crashes at startup with "/usr/bin/calibre, line 20" error
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
*** This bug is a duplicate of bug 1898904 ***
https://bugs.launchpad.net/bugs/1898904
** This bug has been marked a duplicate of bug 1898904
Calibre crashes at startup with "/usr/bin/calibre, line 20" error
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
*** This bug is a duplicate of bug 1898904 ***
https://bugs.launchpad.net/bugs/1898904
This was technically reported first but the other ticket has more
progress already so I'm consolidating the duplicate reports there.
** This bug has been marked a duplicate of bug 1898904
Calibre crashes
Per https://bugzilla.redhat.com/show_bug.cgi?id=1840780#c2 this happens
on python >= 3.8.3. As Focal ships 3.8.5 we get this bug. Juanjo linked
and attached the upstream patch already, which is included in Calibre >=
4.15. Focal ships Calibre version 4.99.4 which I assume is some pre-
release versi
As a work-around for those affected, I can confirm that manually
applying the upstream patch to
`/usr/lib/calibre/calibre/utils/ipc/server.py` does allow Calibre to
start up successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, that's odd. The AUTHORS-SHORT file does not appear in the
wireshark-common package I have on my system. Does removing the
wireshark packages, clearing your apt-cache, and reinstalling the
packages clear up the issue?
Also, why do you think this is lsb-related? I don't see any lsb issues
in th
** Changed in: wireshark (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/1265333
Title:
package wireshark-common 1.10.2-1 failed to install/upgrade: tentative
** Changed in: wireshark (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265333
Title:
package wireshark-common 1.10.2-1 failed to install/upgrade: tenta
** Also affects: overlay-scrollbar
Importance: Undecided
Status: New
** 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/1208583
Ti
Unfortunately I have not experienced this bug since originally filing it
here (so I have not yet started a bisect). It does not appear to be
reliably reproducable even on the same kernel version.
If I can get it to happen with any regularity I will try bisecting.
--
You received this bug notific
Currently installing the first of the bisect kernels. Just a note that
during the install I get:
W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module
radeon
W: Possible missing firmware /lib/firmware/radeon/KAVERI_rlc.bin for module
radeon
W: Possible missing firmware /li
Given that, and the fact that 3.11 includes major radeon changes (in the
form of DPM) and the fact that I have a radeon graphics card, I would
put money on a radeon driver regression.
Tangentially: every time I try and shut-down I get a hard hang as well
(with the current kernel, not yet the bisec
Skimming the linux git changes since rc6 (on which the current saucy
kernel is based) show a couple of radeon-related fixes, but nothing that
claims to be relevant to my r6xx card. I don't currently have much hope
that rc7 will fix anything when it lands.
--
You received this bug notification bec
Both -rc4 and -rc2 are substantially worse:
-rc4 freezes hard immediately on boot-up, it never gets past "loading
initial ramdisk". Modesetting never kicks in. Sysrq+reisub does nothing,
I have to kill the power.
-rc2 boots, but freezes hard immediately on suspend (going in, whereas
the current k
Possibly a duplicate of bug #1248400?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301134
Title:
wireshark stops working when doing almost anything
To manage notifications about this bug go to:
h
This looks like what is expected to happen when you try and run a Qt
application with no X server available... Qt prints a message and
aborts. Not sure what else we're supposed to do in that case.
** Changed in: wireshark (Ubuntu)
Status: New => Invalid
--
You received this bug notificati
Closing invalid as the upstream bug has been marked wont-fix. See the
upstream bug for an explanation.
** 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.
@xatt11 Please don't change the bug status if you don't understand what
it means. As per the numerous comments, this is not actually a bug in
chromium, but in eglibc, which is why the correct status for the
chromium package for this bug is "Invalid".
** Changed in: chromium-browser (Ubuntu Precise
@vanillachip01 The bug occurs regardless of whether the computer is
32-bit or 64-bit. Since the original reporter was running 64-bit, that's
how the bug was filed. Your other comments are not constructive. If you
have issues you want to take up with the community, I suggest the
ubuntu-devel-discuss
@j-jose1197 Please don't change the bug status unless you know what it
means. The correct status for this bug is "Fix Committed" in "aptdaemon
(Ubuntu)" and "Fix Released" in "Aptdaemon".
** Changed in: aptdaemon (Ubuntu)
Status: Confirmed => Fix Committed
** Description changed:
IMPORT
@jmate31 The fix has not been released yet, but it will be released soon
(probably on April 10th). Please be patient until then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971839
Title:
aptd cras
Hi lirel, if you could please attach the pcap file to this bug report so
I can take a look, that would be great. You can then move the status
from Incomplete back to New.
Chances are you're right about the SVN commit, in which case a 1.4.12
SRU will fix it, but I'd like to verify first.
Thanks,
E
@nailartcenter Yes, that's fine. The original report was against
chromium, but as you can see from the list of affected projects the
actual bug is in glibc. Since both chromium and indicator-weather use
libc, both programs can see this bug.
--
You received this bug notification because you are a
Public bug reported:
Please sync wireshark 1.6.6-1 (universe) from Debian testing (main)
Changelog entries since current precise version 1.6.5-2:
wireshark (1.6.6-1) unstable; urgency=high
* New upstream release 1.6.6
- release notes:
http://www.wireshark.org/docs/relnotes/wireshark
As this fixes security issues, should I subscribe ubuntu-security as
well? Or would ubuntu-release be more appropriate? Or both?
Aside: I've not been able to find a clear explanation of who should be
subscribed where for sync requests. If there is already a process in
place could somebody please l
@fabricesp That link seems specifically for new upstream versions with
new features. As this request is for a version that is bug-fix/security
only, do those instructions still apply?
Thanks,
Evan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Fixed after upgrade to Precise.
** Changed in: alsa-driver (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/884546
Title:
[U-100, Realtek ALC1200, Gre
Please note the difference between the status 'Fix Committed' and 'Fix
Released'. 'Fix Committed' simply means that the fix has been identified
by the developers and dumped into the source code repository. It does
*not* mean that the fix is available via the normal update channels.
When a new versi
Please also note the difference between the two bug targets: 'Aptdaemon'
and 'aptdaemon (Ubuntu)'. 'Aptdaemon' refers to the upstream project,
where this bug is 'Fix Released'. This is because upstream has released
a new version with the fix for this bug included. 'aptdaemon (Ubuntu)'
refers to the
@isoloveyko Please do not change bug statuses without understanding what
they mean. This bug should still be 'Fix Committed' in 'aptdaemon
(Ubuntu)', as the fixed packaged has not landed in the repository yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi David,
No, it's not in Precise yet, as the status is only "Fix Committed". This
means that a fix has been identified and created in the source
repository, but is not publicly available yet. When the fix is published
to Precise, the status will move to "Fix Released".
Cheers,
Evan
---
Ubuntu B
Public bug reported:
As per a recent thread on unity-design: log in to a profile with the
launcher set to auto-hide. The current behaviour in this case has two
problems:
1. Discoverability. The launcher loads hidden, so users may not know
where to find it (especially if they're borrowing someone
** Also affects: unity
Importance: Undecided
Status: New
** Also affects: ayatana-design
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934513
Tit
I haven't been able to reproduce since the fix for bug #928014 landed.
Dupe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926208
Title:
bamfdaemon crashed with SIGABRT in g_assertion_message()
To
if you run "LIBOVERLAY_SCROLLBAR=0 wireshark" does that fix it?
If so, this is a duplicate of #1248400.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274179
Title:
wireshark broken trying to captu
How long is "after a while"? Is it possible you are simply running out
of memory? Is it possible for you to produce a backtrack of the crash?
Thanks,
Evan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I actually haven't seen the suspend hang since updating the bios, though
that could still just be dumb luck. I *am* still seeing the lock-ups as
per comment #8, though they don't trigger apport for some reason. I am
currently installing the updated firmware package (bug #1218691 or my
comment #7 on
I still see this fairly frequently, and it is strictly a network-manager
problem. "sudo restart network-manager" causes it to reconnect
gracefully without any problems or kernel magic.
I suspect a race condition, since it only happens about 1/3 of the time
I suspend.
FWIW, I have a totally differ
First I ran "sudo stop network-manager" then ran "sudo NetworkManager
--no-daemon --log-level=DEBUG >nm.log 2>&1" and then I reproduced the
issue. I have attached the complete log output of network-manager from
the initial receive of the "suspend" signal to the point I ctrl-C'ed it
after experienci
Interesting, so it's not even a NetworkManager bug - whatever is
supposed to be sending that signal to nm isn't sending it sometimes, or
is sending it before nm can receive it or something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Based on the liboverlayscrollbar frames in the trace, this is probably
related to bug #1208583. It might even be a duplicate, though the
symptoms and stack trace are slightly different. Regardless, running
"export LIBOVERLAY_SCROLLBAR=0" should probably fix the issue. If it
does I will reassign thi
Not a bad idea, just wrap a shell script that exports the environment
variable?
--
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
Martin, I am seeing this regularly under Unity. Smells like a race
condition to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
[logind] stuck in PrepareForSleep, causing network an
Martin, your package seems to have fixed the problem on my end (after
four successful suspend/resume cycles, which would have been extremely
unlikely previously).
Given that we don't have a consensus on whether the package works or
not, we may have two interrelated issues at play. Yuck :(
--
You
For fun (having read the changelog of Martin's shim package) I
overloaded my system so much that suspend took slightly over a minute to
complete, at which point I was able to reproduce the same failure as
before installing the updated shim package. I have not otherwise
experienced the problem (in n
Still happens with latest kernel. I will note (anecdotally) that it
seems to be substantially more likely if I've done something like a
compile to make the system run hot just before I suspend.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notifica
I have just updated to the latest bios, as indicated by the dmidecode output:
1.0.18
02/24/2009
I will post back if/when I reproduce the issue again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212
Hi Jérôme. Wireshark has had a few issues in the past (for example [1])
with Ubuntu's special overlay scrollbars. Given that liboverlay-
scrollbar is the second frame in the stack trace, I suspect this is also
related.
If you run at the commandline
$ export LIBOVERLAY_SCROLLBAR=0
$ wireshark
And
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212041
Title:
suspend/resume failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
Public bug reported:
Suspend appeard to work fine. Resume came back, monitor backlight turned
on and disk spun a bit, but no visible graphics or reaction to input.
Had to alt+sysrq+reisub to force a reboot.
This is a regression since the update to kernel 3.11.0 a few days ago.
ProblemType: Kerne
Looking at the changelog for the BIOS, there do not appear to be any
related fixes between 1.0.15 and 1.0.18 so I highly doubt the upgrade
will fix the issue (which does not seem consistently reproducable
anyways). I will do it to be sure, but it may take me a while to get
around to it.
--
You re
*** This bug is a duplicate of bug 1212041 ***
https://bugs.launchpad.net/bugs/1212041
Public bug reported:
Duplicate of #1212041 with later kernel (rc7) in case the updated trace
is useful.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
Still occurs with rc7 (I filed a dupe and marked it as such, in case the
updated apport trace is useful).
Moving back to "Confirmed" since I have provided all the information I
can think to provide at this point. Joseph, Christopher, please advise
on next steps.
** Changed in: linux (Ubuntu)
Public bug reported:
Please sync wireshark 1.6.7-1 (universe) from Debian unstable (main)
New upstream version, bug fixes only.
Changelog entries since current precise version 1.6.6-1:
wireshark (1.6.7-1) unstable; urgency=low
* New upstream release 1.6.7
- release notes:
http:
@ronsteed-o Depends on how long the change takes to build and propagate
to whichever mirror your using. The change is already on the main
(Canonical-hosted) mirror, so most other mirrors shouldn't be far
behind. Note that the bug may appear one more time after applying the
fix if you still have an
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001821
Title:
[regression] MSI Wind U-100 hangs on resume from suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
Public bug reported:
Worked fine in Oneiric. Upon upgrading to Precise, approximately 3/4
suspends will hang upon resume. Mouse is movable, and in fact the cursor
changes correctly to I-beam when mousing over text that was already on
the screen, however nothing responds to mouse or keyboard input.
Please set the status back to 'New' when you provide a sample capture
file.
Thanks
Evan
** Changed in: wireshark (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/bug
Done a bit of additional debugging:
- pressing Print-Screen when it's frozen does produce the camera noise,
but no visible change to the screen, so keyboard input is still being
tracked (to a point)
- running unity --replace from a VT fails, as it claims to fail opening
the display.
- killing co
Wireshark does nothing odd with it's desktop file or windows, so this is
almost certainly a bamf bug (the app that handles the sidebar tiles)
rather than a Wireshark bug. Reassigning.
For the bamf devs who take a look at this: wireshark opens a splash
screen that bamf picks up on, which disappears
The attached file opens fine on Wireshark 1.6.7 on Windows 7. I haven't
tried it on Ubuntu yet, but I'm leaning towards a libpcap bug, since
that's the only significant difference between Wireshark on Ubuntu and
Wireshark on Windows (aside from GTK, which is rather obviously
unrelated).
--
You re
Public bug reported:
Was just running update-manager as normal and this popped up. Had to
clean things up manually in synaptic.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: valac-0.16-vapi (not installed)
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961740
Title:
package valac-0.16-vapi (not installed) failed to install/upgrade:
trying to overwrite '/usr/share/vala-0.16/vapi/ccss-1.vapi', which is
Public bug reported:
Ever since upgrade to 5.8.0 this afternoon, logging in to Unity 3D boots
me back to login screen. 2D works fine.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963465
Title:
Can't login to Unity since upgrade to 5.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+b
Logged in as Unity-2D, ran unity --debug --verbose and captured stdout
and stderr to a file, as attached, Looks like compiz is missing some
files?
** Attachment added: "unity --debug --verbose log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/963465/+attachment/2925530/+files/unity.deb
Debian just fixed this in 1.6.5-2 (I expect launchpad will pick up the
change in the DBTS shortly). Do we need a sync request or something now?
It's only doc changes and the new icon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Public bug reported:
Problem is likely in "54_enable_alt_tap_in_shortcut.patch" in gnome-
control-center.
1. Initially, note that both HUD (using left alt) and window management menu
(using alt-space) work properly. The HUD shortcut in Keyboard Settings is
listed as "Alt L".
2. Click on the set
** Also affects: gnome-control-center
Importance: Undecided
Status: New
** Project changed: gnome-control-center => gnome-control-center
(Ubuntu)
** Description changed:
- (This perhaps should be against gnome-control-center instead of unity?)
+ Problem is likely in "54_enable_alt_tap_
Seems related to this:
http://projects.comum.org/guake/ticket/76
** Summary changed:
- Changing HUD key from 'Alt' to 'Alt' changes behaviour
+ Changing HUD key from 'Alt' to 'Alt' changes behaviour when numlock is on
** Description changed:
- Problem is likely in "54_enable_alt_tap_in_shortcu
With Numlock Off:
---
KeyPress event, serial 36, synthetic NO, window 0x421,
root 0xbd, subw 0x0, time 542002, (434,589), root:(488,641),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLooku
Possibly a dupe of bug #925602 ?
I will report back once I've updated to the latest kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902420
Title:
AR922X Wireless flaky since upgrade to Precis
*** This bug is a duplicate of bug 925602 ***
https://bugs.launchpad.net/bugs/925602
** This bug has been marked a duplicate of bug 925602
[Asus Eee PC 1215N] Wireless is slow and unreliable (AR9285)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Wireshark doesn't do anything unusual with the UI (we use the same GTK
toolkit as everything else) so I suspect this is not a Wireshark-
specific bug.
Feel free to re-assign to the kernel or graphics driver, or close as you
see fit.
--
You received this bug notification because you are a member
As mentioned in our previous discussion: it may simplify your life by
moving to the last stable 1.6 release (1.6.16 if I recall correctly) and
only applying extra patches on top of that. Otherwise you will just end
up duplicating a lot of work that the Wireshark team already did when
1.6 series was
For what it's worth: Wireshark upstream releases regular micro-release,
supporting each major version for at least two years. I have considered
applying for an SRU MicroReleaseException [1] a couple of times in the
past, but never had the time to really dig in and figure out all the
requirements.
Hey there, I'm a wireshark core dev and kind of the unofficial point of
contact for Ubuntu/Wireshark (along with Balint Reczey, who maintains
the upstream Debian package).
As far as I know, Balint has been backporting the necessary CVE fixes
into the wireshark packages for Debian stable. For preci
Thanks for the report, I've uploaded a potential fix to
https://code.wireshark.org/review/6330 although I haven't had a chance
to try reproducing myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hi, thanks for the detailed report. Just so you're aware, I have added
the appropriate upstream fixes to Wireshark's stable backport list, so
Wireshark 1.10.6 (whenever it is released) should compile correctly
without any patches.
Unfortunately Wireshark doesn't have an Ubuntu-specific maintainer
Sorry, missed the ubuntu-sponsors subscription.
Debian is currently building with GTK 3.8, so it works for them (for
now). I don't know when they plan to migrate to 3.10, but it's been out
since September so I expect they'll move soonish.
I believe Balint (debian maintainer) monitors ubuntu bugs
This appears to be already tracked upstream as bug 9179 - based on the
analysis there it is a bug in Cairo, but we have a workaround in trunk
already that just needs backporting.
** Bug watch added: Wireshark Bugzilla #9179
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9179
** Also affect
I believe this is a GTK-3 specific issue - my GTK-2 wireshark build on
Trusty does not exhibit this problem. Is there a way for you to try a
GTK-2 build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I can't speak for the greeter itself, but it is definitely listing media
players in the new greeter-like lock screen, which is a similar problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280378
Wireshark uses some unusual GTK widgets and has never shown any of these
symptoms on systems not using overlay scrollbars, so this is almost
certainly a liboverlay-scrollbar bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I haven't had that hardware in a couple of years, so this can expire
unless anybody else is still experiencing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/578460
Title:
[Karmic,Lucid] 82G33/G3
Well, between the new bios, new firmware, and 3.11.3 kernel (whose
changelog includes a whole mess of radeon-related fixes) something seems
to have fixed this. I haven't had any lock-ups at all in a few days now
(and the only suspend-related bug I see now is #1184262 which is
entirely unrelated).
What component is *supposed* to be sending it that signal? I have
noticed that in cases where this bug appears, other power management
options also fail - trying to suspend again from the gear menu does
nothing, I have to run pm-suspend from the cli. This indicates to me
that some whole underlying
Yes, looks like a dupe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
network-manager has decided that networking is disabled, cannot be re-
enabled from lightdm
To manage notifica
1.10.6 is quite old as far as upstream Wireshark versions go. Is it a
workaround at least to download and use a more recent Wireshark that
might already have this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
No longer exists in Saucy that I can determine, and lo-menubar has been
superseded anyways by something else.
** Changed in: lo-menubar
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Marking as Fix Released, as 1.8.2 (with this bug fixed) is in 12.10
(Quantal).
** Changed in: wireshark (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Closing this as opinion, as even if Linux were to offer more fine-
grained security controls we might not use them (due to the security
concerns Balint mentioned).
** Changed in: wireshark (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member
@tecnicos-extreme-micro Which version of Ubuntu/Wireshark did you see
this bug on? If Ubuntu 10.04 with Wireshark 1.6.7 could you please check
if a later version of Wireshark fixes the bug as I suggested in comment
#3?
** Changed in: wireshark (Ubuntu)
Status: Confirmed => Incomplete
--
Y
I am marking this bug as "Fix Released" because the version of Wireshark
in Quantal (12.10) has this bug fixed. This does not mean that the bug
is fixed in Precise (12.04) - it's not.
To fix this bug in Precise will require a stable release update,
probably to Wireshark 1.6.12. The following link
Hi Mario, thanks for the report. Could you please try and provide a more
detailed set of steps you use to reproduce the problem? Also, if the
crash occurred while capturing or reading a capture file, attaching that
file is often helpful.
Finally, be aware that the version of Wireshark that is in t
Hi Mario, thanks for the additional information. I have not been able to
reproduce the issue with 1.6.12 (the earliest version I have access to)
so either it was fixed by then or there's something else going on.
The alleyoop log you provided doesn't appear to contain the crash itself
- if you coul
Still exists on latest Raring, for what it's worth.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045353
Title:
Commands are not displayed in the HUD
To manage notifications about this bug go to:
I can confirm this behaviour with the latest Wireshark package in
Oneiric (the Ubuntu development version). I have reported the issue
upstream at https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6367
---
Ubuntu Bug Squad Volunteer
https://wiki.ubuntu.com/BugSquad
** Bug watch added: Wireshark
To all those who have been wondering why the bug says "Fix Released" but
who are still encountering the issue:
As explained by Eliah in comment #33:
"This bug is not closed. A fix has been committed upstream, but it is
not yet available as an update to Oneiric. Once the status in Oneiric
changes
I just saw this again after updating and rebooting.
apt-cache madison reports:
apt | 0.8.16~exp5ubuntu12
So I do have the version which was supposed to contain a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
1 - 100 of 270 matches
Mail list logo
