I haven't been able to find other actual bugs/issues describing this
issue, but there are threads on reddit and such that seem to indicate
that this is a wayland/gnome42 issue, and that it affects all
distributions.
Still a problem here. I'm on 22.04 with all updates (including proposed)
installed, latest firefox snap (99.0-2, rev 1188).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947210
Title:
Firefox Snap
While the problem might be in snapd, Firefox is still very much
impacted, when it comes to the decision to ship 22.04 LTS without a deb
version of Firefox to fall back to. In my experience, this is just one
of many ways the experience with the snap version of Firefox is not on
par with the
This is still an issue in Ubuntu 21.04 (development, as of March 30,
2021)
It looks like people have been complaining about this for years, and
while some people have tried to fix it, those fixes never made it in.
Surely it must be of some type of urgency to support 2FA one-time
passwords in the
I am no longer able to reproduce the crash after installing the proposed
fix! Looks good 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/1918033
Title:
gnome-shell crashed with
Problem occurs on Wayland as well as Xorg.
Please let me know what kind of info you need.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918127
Title:
gnome-shell crash when using panel
To manage
Public bug reported:
Whenever I perform an action in the Gnome Panel (Activate a VPN has 100%
failure-rate, but I have seen it when clearing notifications and other
things too), the entire session crashes and I'm back at login.
I'm running gnome-session on Hirsute.
journalctl
Never mind - Somehow my local package simply looked newer from a
versioning perspective. I found the right version and as far as I can
tell the problems are gone in this version.
I have not seen any of the dbus messages and roaming works better (less
erratic) here.
Thanks a lot for getting this
I've been looking for the package but cannot seem to find it for
testing. Please help me find it and I will test it immediately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879087
Title:
dbus
So in my case, my VM was configured with only 256MB of memory. This
caused no problem on the normal -virtual kernel but caused all sorts of
problems when I installed -lowlatency in the guest.
Upgrading to 384MB solved the problem reliably here, so perhaps this is
not the same thing afterall.
-
Kernel version 5.4.0-37-lowlatency, btw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
To manage notifications about this bug go to:
I have an LXD Virtual Machine refusing to boot after installing the
-lowlatency kernel on it. Sounds like these _might_ be related, so
here's my info. I'm on a NUC too, btw.
Host: Ubuntu 20.04 LTS, LXD 4.2 snap (running -lowlatency)
Guest: Ubuntu 20.04 LTS
The guest was running without problems
Thank you for taking care of this so swiftly.
I don't believe I have much to add to the test-case. From testing
locally I can see that the warnings disappear from the log and the
connection _seems_ more stable. I underscore _seems_ because I have not
been able to figure out which other parts of
Public bug reported:
When using this version of wpa_supplicant with my company
WPA2-Enterprise wireless setup, I'm experiencing far too frequent
roaming events (even when not moving around) accompanied by hiccups in
connectivity. I also see these messages in the wpa_supplicant log:
dbus:
On a fully updated Ubuntu 19.10, I feel most of my problems occur, when
copying from a Wayland application, and pasting to an XWindow
application. Most of the time, that doesn't work at all.
As an example. Running my Firefox as a native Wayland application, I am
experiencing problems copying a
I have started a dialogue on the TZ mailinglist to perhaps have the
change (WGT/WGST at least) reverted. That's my goal anyway, so we'll see
how it goes.
/Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi guys,
The removal of WGT/WGST from tzdata is crazy to me. Living in Greenland,
I can imagine a bunch of different issues this will cause, so I'll try
to figure out what is going on and what possibilities we have of
rectifying it. Starting with upstream.
/Thomas
--
You received this bug
Public bug reported:
Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed from
date command but instead just "-03". Problem is evident in PHP
applications too, which now think we're in Sao Paolo.
This appears to have changed with latest tzdata update or perhaps in
combination with
Looking through the code, these outputs may differ because of the
different ways to authenticate... I'm not sure but both messages are
certainly present in the latest openvpn code.
FWIW, I'm connecting to an OpenVPN-AS solution with Certificates and
Password
--
You received this bug
Looks like the message that's being looked for might have changed:
This is from my log now:
AUTH: Received control message:
AUTH_FAILED,CRV1:R,E:93NBZNaOH799HLoxv7tWefldc8JtIpbf:eHRod3Q=:Enter PASSCODE
But based on the commit, it might be looking for:
This is from the commit below:
This doesn't seem to work for me on Ubuntu 17.10:
openvpn 2.4.3-4ubuntu1
network-manager 1.8.4-1ubuntu3
network-manager-gnome 1.8.4-1ubuntu3
network-manager-openvpn 1.2.10-0ubuntu2
network-manager-openvpn-gnome 1.2.10-0ubuntu2
When activating an OpenVPN connection that's challenge/response
@Vincent, re the "If lookups are routed to multiple interfaces, the
first successful response is returned", this is indeed the problem with
systemd-resolved as I see it, as that method will never be stable for a
split DNS setup... You can never reliably predict if you'll get a good
or a bad IP for
To clarify... I believe NetworkManager is the culprit here - or systemd-
resolved is fundamentally broken (i don't have the working knowledge to
guess which it is). So my comment #44 is more about getting a working
system than addressing any issue with systemd and/or NetworkManager.
--
You
So I have come up with a working solution that actually solves all MY
needs in this regard. Hopefully it will be of use or inspiration to some
of you guys too...
Part 1 -- Switch NetworkManager to use dnsmasq (this will NOT work with
resolved!)
# apt-get install dnsmasq-base
Add dns=dnsmasq
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
This is not fixed, but is marked as a duplicate of #1624317
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You received this bug
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
** This bug is no longer a duplicate of bug 1629611
dns server priority broken
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
** This bug is no longer a duplicate of bug 1629611
dns server priority broken
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You
For the record, this continued to bother me until I got a replacement
laptop. I received an exact identical new laptop and have never since
seen this issue... Hardware fault and nothing else!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
** This bug is no longer a duplicate of bug 1629611
dns server priority broken
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You
I'm on 17.04 too and suffering from this issue for a while.
As I understand this issue, the problem may actually very well be in
Network-Manager rather than in systemd-resolved, but the problem is
indeed very visible with resolved.
Here's how I experience the problem (the root of my problems are
@Tim - What Patrick said... Or prevent the kernel package from being updated
until the fix is included:
https://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Okay, so MIGRATION is indeed enabled on the mainline kernel too and that
possibility has been ruled out - So we're not chasing ghosts. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
There must be a better way to do this...
All of these issues seem to arise from a BUG event in swapops.h:129. That
particular spot is a section that's only active, when the kernel was built with
CONFIG_MIGRATION=y. So first step is probably to verify that CONFIG_MIGRATION
is even enabled for
Seems to work in 1.4.4-1ubuntu3 in 17.04 at least... Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629611
Title:
dns server priority broken
To manage notifications about this bug go to:
Okay,
Since updating the BIOS of my Lenovo T460s laptop from version 1.15 to
1.20, I've not seen this issue once.
Since I've not been able to successfully reproduce the error at any
point, I can't say for sure that the problem is gone. It has been a
weeks time, however, which is certainly a
The most promising so far is a brand new BIOS upgrade for my system. Haven't
seen the problem since upgrading 4 days ago.
Not quite ready to declare it solved, but certainly looks promising.
Happy holidays.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That is certainly a possibility, but unfortunately returns us to a state
where applications have to be restarted when nameservers change (glibc
resolved.conf issue). That's probably even worse in my situation at
least.
--
You received this bug notification because you are a member of Ubuntu
Unfortunately not much traction here, and this appears to annoy people
across distros.
In the meantime, an ugly hack is to manually add all internal domains to
the NetworkManager VPN config file's dns-search= parameter:
dns-search=domain1.lan;domain2.lan;domain3.lan;example.com;
This causes
Please let me know what kind of info you need, in order to find a
resolution to this issue - I can't imagine it's a hard one to solve,
given the right information. At the very least, determining if this is
indeed a hardware/firmware bug or a kernel bug, would be a HUGE step in
the right direction.
Hmmm, so several crashes again today while on battery. Even with
power/control set to "on" rather than auto. I'm on 4.9-rc8 btw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641322
Title:
Wow - Long message, but what I got from it was "I need to see a debug
log", correct? I'll attach that...
I'll also point you to the problematic part:
Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1915]
dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain
FWIW, this appears to work around the issue:
Create file /etc/udev/rules.d/90-nvme-power.rules :
---
KERNEL=="nvme*[0-9]n*[0-9]", ATTRS{model}=="SAMSUNG MZSLW1T0HMLH-000L1*",
ATTR{device/power/control}="on"
---
On my system at least.
I'm sure the kernel should somehow blacklist settings that
Okay - Crashed 3 times this morning on rc7 AND rc6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641322
Title:
frequently lost connection to nvme
To manage notifications about this bug go to:
I'd really like to have this issue resolved, so anything you guys need
to get closer to the culprit, just let me know. So far, 4.9-rc6 mainline
build appears stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Darn it... Just had the crash on rc7. Going back to rc6, thinking it may
be workload related... Will report back...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641322
Title:
frequently lost
Problem not seen on 4.9-rc6 mainline. Moving on to 4.9-rc7 mainline
now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641322
Title:
frequently lost connection to nvme
To manage notifications
I haven't found a positive fix for this issue in 4.9-rc6, but FWIW, I've
been running 4.9-rc6 for a couple of days without encountering this
issue.
I'll let you know how this goes after further testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've not found a positive match, but this MIGHT be related to the
following upstream bug.
https://bugzilla.kernel.org/show_bug.cgi?id=112121
** Bug watch added: Linux Kernel Bug Tracker #112121
http://bugzilla.kernel.org/show_bug.cgi?id=112121
--
You received this bug notification because
Okay,
I've been running on 4.9-rc5 mainline all day, at work, with no issue at
all. After I take my laptop home, boom! Same problem. This is likely
triggered more often at home, where I'm on battery more than I am at
work, causing more aggressive power savings to take place.
In any case, my
I've installed latest mainline build and awaits the issue... I have
definitely seen the issue with the 4.9-rc4 mainline build, but the rc5
just yet... I'll be back with an update in a few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Captured dmesg output from the error happening"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+attachment/4776493/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Since before the release of Yakkety Yak, I've been having problems with
a new laptop with a Samsung nvme device: 05:00.0 Non-Volatile memory
controller: Samsung Electronics Co Ltd Device a804 (prog-if 02 [NVM
Express])
For whatever reason, I sometimes (often) loose
Here's the thing,
I'm on 16.10 which has the debian equiv listed as stretch/sid and my
network-manager version is 1.2.4-0ubuntu1.
Looking at Debian stretch and sid, they have network-manager packages in
various versions but not 1.2.4.
Furthermore, since Ubuntu employ their own patches,
I'll do it :)
Any helpful pointers to which package/version i should reference, since
I don't have the real debian version of this package anywhere?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, that does not seem like the problem to me - Or it's not described
correctly. I can't seem to find a proper match in that list.
resolv.conf is not the issue here - the problem is in the DNS servers
that dnsmasq uses. I.e. one is added to dnsmasq when my wireless
connection comes up, and when I
This bug seems to bite me in a slightly different way. Please let me
know if you feel that this is really a separate bug...
Also, this is happening on Yakkety - network-manager-1.2.4-0ubuntu1
When I connect to my work VPN, I'm not using split-tunnelling. Still the
DNS resolution is split,
Public bug reported:
network-manager: 1.2.4-0ubuntu1
Yakkety appears to have switched back from resolved to dnsmasq, but it seems
server priority/order is broken.
Example: In split DNS setups, connecting to VPN will not cause us to
query the DNS provided by the VPN first (or only), which
Public bug reported:
2-factor authentication is all the rage these days, so we should to be
able to prompt for the Challenge Response when needed... Right now the
behaviour looks more like a password failure and it doesn't work (I'm on
Gnome3).
OpenVPN transaction that is probably what we need
open-vm-tools also chokes on this, when freezing filesystems for a
quiesced snapshot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/499773
Title:
Race with ureadahead can mean that
Hmmm I can't seem to find it documented anywhere, but last time I needed
this to work was in the good old sysvinit days and it may have even been
on a different distro. Sorry for not brushing thoroughly up on this,
prior to filing this bug.
I have checked with CentOS 7 and it has the halt.local
You're absolutely right - Changed to systemd
** Package changed: transmission (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also all other distros, regardless of init system, appears to have this
file somewhere. Bad solution IMHO
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
/etc/halt.local has become
Fair enough...
As mentioned earlier, this may be from a systemv time and perhaps from
Red Hat, I'm not sure. I do know that /usr/sbin/halt.local works in both
Wily and in debian 8 out of the box, the file is just located in dpkg-
managed space, which makes no sense.
Look, I'm not actually
Alright - Got your comments late, let me try that out
Are these targets documented somewhere, so it becomes clear exactly what
is started when?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532553
systemd.special(7) explains what they are, but if I could somehow get
the correlation between targets, that'd be cool
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
/etc/halt.local
In that case we are missing documentation for the shutdown/halt procedure more
than ever.
Very often halt.local is where we'd do stuff like powering off UPS outlets, to
handle power-outage scenarios properly. It may not have been documented or
placed ideally, but AFAIKT, it's actually always
Thowing user-managed executables in /lib/systemd/system-shutdown/ is not
much better than editing /usr/sbin/halt.local. Is there an /etc or a
/usr/local based version of this directory available somewhere, that
will work out of the box, then that will work for me, i guess.. I'll try
it out at
Thank you for your input. It's not working how I want it to right now,
but I'm confident it can be done. I need to read up on systemd for this
to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was wrong. It appears as if the XFS filesystem on / is the actual culprit
here.
The way XFS works, makes it lose last-second changes such as the new settings
file written by transmission-daemon, whet the power is cut after halt. I've
added a "sync" to my UPS power-off script and everything
After this, I have no indication that anything should be wrong with
transmission-daemon regarding this, so I'm closing the case.
** Changed in: transmission (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Ubuntu-15.10, amd64
systemd-225-1ubuntu9
transmission-daemon-2.84-1ubuntu1
I've noticed more than once, that "halt" can cause transmission-daemon
to loose it's settings. AFAIK, "halt" is not that different from
"poweroff" or "reboot" in regards to the shutdown sequence, so
Public bug reported:
Ubuntu 15.10, amd64
systemd-225-1ubuntu9
/etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO is
bad for a couple of reasons.
1) This is not where it's supposed to be
2) Locally modified (non-dpkg managed) scripts under /usr is bad
I have not been able to
I'm having this issue on Wily today - Occurs on Wily kernel 4.2.0-15 but
not on 4.2.0-14 for me.
Bug #1503738 mentions this bug # as a duplicate, but while it probably
is the exact same issue, it's on a very different kernel/distro version
for me. Please let me know if the fix is automatically
I'm on a virtual machine and experiencing the same thing. The problem
seems to be covered pretty well in pages mentioned in #8.
My problem in more detail is trying to kexec the 3.16 kernel provided by
linux-generic-lts-utopic in trusty (from original 3.13 kernel, to allow
normal kernel updates on
I have the same problem on several different machines, both on 3.11.0-20
and 3.11.0-24.
For me it only happens on boot, and not entirely consistantly -
Sometimes it works, sometimes it crashes. It does crash pretty often
though, and I'm trying to find a way to reproduce consistently.
[
Without too many details, the problem seems to be triggered by some sort
of race condition between the loading of the sunrpc module and using it
(mounting the rpc_pipefs filesystem). This can happen in two places, as
far as I can tell... in /etc/init/gssd.conf and /etc/init/idmapd.conf.
On my
Lots of talk about bandwidth, but (IMHO) at least as interesting is ping
times (because the results are instantly visible):
I'm on a ThinkPad T431s with an Intel Corporation Centrino Advanced-N
6235 (rev 24)
3.13.0-24-generic without PM (pinging my AP):
$ ping -c 5 192.168.8.2
PING 192.168.8.2
Comfirmed on HD 7400M Series
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon HD 7400M Series
OpenGL version string: 4.2.11986 Compatibility Profile Context
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1054499 ***
https://bugs.launchpad.net/bugs/1054499
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058015
Title:
compiz
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057833
Title:
soffice.bin crashed with SIGSEGV in Menu::~Menu()
To manage notifications about this bug go to:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056067
Title:
java crashed with SIGABRT in
Java_com_sun_java_swing_plaf_gtk_GTKStyle_nativeGetXThickness()
To
Public bug reported:
In gnome-terminal CTRL-'+' and CTRL-'-' is supposed to zoom in and out
respectively:
Zoom in should: increase the font size and resize the window to match the new
font size (keep rows and cols consistent)
Zoom out should do the exact opposite: reduce the font size and
This is on quantal (up to date as per now) - Problem existed on
precise last I checked too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046822
Title:
Zooming does not work corrently
To manage
Not a firefox bug but a missing driver AFAICT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951246
Title:
13b1:002f Linksys AE1000 v1 802.11n [Ralink RT3572] not usable in
network manager or
When will a kernel with this fix be released? Pending that, is there
somewhere to download a daily kernel package for Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019561
Title:
148f:5370
Any reason why this fix has not gone into final precise?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/930916
Title:
amavis start-stop script fails to stop amavisd
To manage
Any reason why this fix has not gone into final precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930916
Title:
amavis start-stop script fails to stop amavisd
To manage notifications about
dante-client is not even installable in precise atm. Please let me know
what I need to provide you with, to have this fixed.
Please take a look at
https://launchpad.net/~tmus/+archive/ppa/+sourcepub/2249432/+listing-
archive-extra - This package installs and works on precise.
--
You received
I have this exact problem on a freshly installed Precise.
This is what I had to do, to fix the problem:
in /etc/samba/smb.conf add the following to the bottom of the [global]
section:
client lanman auth = yes
client ntlmv2 auth = no
I could gvfs-mount a Windows 2008 share, but not an Alfresco
Answering myself (Comment #4), the 0.12.5 package does not include an
initscript for sfacctd og nfacctd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905453
Title:
Please upgrade for precise
To
Jamie, does the 0.12.5 package include initscripts for nfacctd and
sfacctd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905453
Title:
Please upgrade for precise
To manage notifications about
Public bug reported:
Dante (at least the client portion - socksify) has been broken on the
past few releases of Ubuntu.
Socksify would throw an error, trying to preload libraries (more details
on this if you need it - see Bug #857598)
Please make sure this works for precise - And why not update
Public bug reported:
There's a new upstream version of pmacct available, that would be great
to get in precise.
More urgent though, is the need for an initscript for sfacctd, nfacctd
(only one for pmacctd is included, even though sfacctd and nfacctd are
also provided by the package).
As far as
In my case, I seem to loose the windows controls some times. Some times
they are there... My feeling is, it usually has something to do with
leaving fullscreen mode...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Running: Ubuntu oneiric (development branch), Unity 4.12.0-0ubuntu2.
Task switcher gets stuck behind all the other active windows. Minimizing
all other apps, makes it visible and shows it's actualy working fine -
But it really should be in the foreground to be really useful.
Any news here?
Could this problem be related to the missing libvideo.so Compiz Video
Playback plugin? I'm having all these problems as well on Natty, using
fglrx.
Mplayer works sort of okay in fullscreen with gl output, but nowhere
near optimal. Windowed gl output as well as xv output
Public bug reported:
Binary package hint: evolution
Just connected by MAPI to Exchange 2010 server, Evolution was
downloading messages and crashed during the initial sync-stuff...
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu5
ProcVersionSignature: Ubuntu
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/652821/+attachment/1662065/+files/Dependencies.txt
** Attachment added: Disassembly.txt
https://bugs.launchpad.net/bugs/652821/+attachment/1662066/+files/Disassembly.txt
** Attachment added: ProcMaps.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33350465/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/33350466/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/33350467/ProcStatus.txt
--
Evolution
Public bug reported:
Binary package hint: evolution-mapi
I have set up an account, connecting to my company Exchange 2007 server,
using evolution-mapi.
When opening Evolution, it retrieves message- and folder lists okay, but
when I click on a mail to read it, evolution crashes almost every
100 matches
Mail list logo
