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
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
*** 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
*** 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,
*** 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,
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
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
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
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.
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
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
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.
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
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.
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:
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.
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
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]
** 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:
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
** 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
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
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 :(
--
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
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.
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 this
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
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.
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
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).
First I ran sudo stop network-manager then ran sudo NetworkManager
--no-daemon --log-level=DEBUG nm.log 21 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 experiencing this
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
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
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
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.
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
** 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
*** 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)
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
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
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
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
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
** 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:
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:
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
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
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:
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
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
@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
--
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
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.
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
This just came back in Raring. Could someone with permission please re-
open?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005677
Title:
Re-emergence of Gtk-CRITICAL **: IA__gtk_widget_style_get:
This bug was reported against Natty (version 11.04) which is no longer
supported. Has someone been able to reproduce this in a supported Ubuntu
version?
** Changed in: wireshark (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of
The similar (identical?) dropbox bug has just been fixed in the latest
stable dropbox [1].
Perhaps it's worth pinging them to ask what they changed?
[1] https://www.dropbox.com/release_notes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Christopher, I don't see how the information from the
DebuggingKernelSuspend page would be helpful - the system is not failing
to resume, it is simply slower after resuming.
I will try an upstream kernel when I have a chance.
--
You received this bug notification because you are a member of
Marking as incomplete. Please confirm that a later version of Wireshark
fixes the problem, or provide more detailed steps to reproduce.
Thanks,
Evan
** Changed in: wireshark (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Max, I'll have to dig out my 1.6 branch before I can take a closer
look, but you should know that the version of Wireshark in Precise has
not changed since April 12th, 2012, when the current version was
uploaded :) Note that that's before Precise was officially released, but
after you upgraded
So I haven't had a chance to test yet, but I believe that this was
probably fixed for 1.6.8 in the following commit:
https://anonsvn.wireshark.org/viewvc?view=revisionrevision=42075
To get an updated wireshark into Precise (probably 1.6.11, as that's the
latest stable in the 1.6 series) you can
I am currently running the latest Quantal, and although I hadn't thought
of this bug in about a year I suppose it is still happening, just much
less noticeably because the rendering speed in general has improved so
much. It's also happening consistently on every suspend/resume I
remember in the
Hi Kevin, please don't change the status of the bug without providing an
explanation, and please don't assign the bug to yourself unless you plan
to provide a fix.
Thanks,
Evan
** Changed in: libindicate (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: libindicate (Ubuntu)
On Mon, Sep 24, 2012 at 7:48 PM, Daniel J Blueman dan...@quora.org wrote:
In Ubuntu 12.10 pre-release, I've frequently been observing ext4
recovery has been needed after reboot [1].
This clearly isn't expected, however could be a side-effect of eg
incomplete flushing after unmount before the
I just reread the README.debian file and didn't find it particularly
non-obvious. The very first thing it does is say that there are two ways
of getting permissions to capture packets. It then lists those two ways
(explicitly mentioning which is default) and says that to switch between
them you
I am seeing a very similar issue with the Dropbox indicator applet, and
after much experimentation I believe both issues (network-manager and
dropbox) are caused by a race condition within libindicate itself. I
have opened a libindicate task for this bug, hopefully someone from that
project will
** Also affects: libindicate
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/965895
Title:
After boot, NetworkManager indicator menu only shows four
So, taking a look at your /etc/group file, there are a few oddities.
Wireshark is doing the Right Thing here, as forcing the removal of the
wireshark group would likely leave you unable to log in.
I assume that you were doing some manual group manipulation to try and
get capture to work without
Also, works-for-me in Quantal, if that's worth anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020656
Title:
Wireshark does not have an icon on the Unity panel
To manage notifications
Reassigning to bamf, since it's in charge of picking the icon, and it
used to work with this exact version of Wireshark.
** Package changed: wireshark (Ubuntu) = bamf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Tried to upgrade via synaptic and this popped up. Hopefully apport got
something useful.
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: compiz-gnome 1:0.9.7.8-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019059
Title:
package compiz-gnome 1:0.9.7.8-0ubuntu3 failed to install/upgrade:
trying to overwrite '/usr/share/gconf/schemas/compiz-ccp.schemas',
Hi Ken, please don't confirm your own bug. Generally we need someone
other than the original reporter to reproduce an issue before it can be
marked confirmed.
I've tried a few things and I haven't been able to reproduce the
symptoms you saw. Could you provide a more detailed step-by-step case to
Thanks for the video, I was able to reproduce it with that information.
The don't confirm your own rule isn't about competence or time the bug
has been open. It is just because different people have different set-
ups. As explained at https://wiki.ubuntu.com/Bugs/Status:
Confirmed bugs require
Marking fixed per dmarks' confirmation.
** Changed in: bamf (Ubuntu)
Status: Incomplete = 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/1002724
Title:
Wireshark doesn't stay in
This is fixed for me with the latest update to Bamf in Precise
(0.2.118).
If anyone else can confirm it's fixed, mark the bug as Fix Released.
If anyone else can still reproduce and you're sure you have the latest
version of Bamf, mark the bug as Confirmed again.
** Changed in: bamf (Ubuntu)
I'm going to take a guess that the build system is looking for
libraries in the old locations, rather than the new multiarch
locations. Try playing around with -L options to the linker (possibly
missing /lib/x86_64-linux-gnu)?
Evan
On Tue, May 29, 2012 at 8:58 AM, John Gabriele jmg3...@gmail.com
Switching to unity-2d works around the problem. Definitely a
compiz/unity issue. Reassigning to compiz, since that seems more likely.
** Package changed: xorg (Ubuntu) = compiz (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No longer able to reproduce with current Precise.
** Changed in: simple-scan (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/906640
Title:
simple-scan
@James: It's supposed to change depending on the wallpaper. This bug was
about it picking a wildly inaccurate colour (ie one that wasn't anywhere
close to what was in the wallpaper).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
This bug was already reported and fixed upstream at [1]. Wireshark as
built from current SVN decodes the sample correctly.
Ubuntu will automatically pick up the fix when Wireshark releases 1.8
and we sync it in from Debian.
If you want the fix in Precise, you can manually run a Wireshark
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.
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
--
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:
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
On Wed, May 9, 2012 at 11:30 AM, Sivan Greenberg si...@omniqueue.comwrote:
Hi All,
Some of you might remember me, some of you won't. I used to be part
of the Ubuntu community and loved every minute of it. I've been drawn
to some other open source projects since then, but the apparent
On Tue, May 8, 2012 at 11:19 AM, Paul Smith p...@mad-scientist.net wrote:
I'm trying to run a program under Wine in my Ubuntu 12.04 64bit fresh
installation. When I run it I get this error:
p11-kit: couldn't load
module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
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,
On Tue, Apr 24, 2012 at 6:39 AM, Christoph Mathys erase...@gmail.comwrote:
I just encountered some problems with very long boottimes on precise.
failsafe.conf just hangs until the timeout has elapsed.
The culprit seems to be that I define interfaces in
/etc/network/interfaces that do not
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,
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,
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
** 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
1 - 100 of 302 matches
Mail list logo
