Correction. This bug report should apply to msmtp-mta package which
creates the symlink from sendmail to msmtp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893268
Title:
msmtp package should use
ng, please?
Best regards,
Heikki Orsila
** Affects: msmtp (Ubuntu)
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/1893268
Title:
msmtp package should
4.4.0-186 is already released. Both 4.4.0-185 and 4.4.0-186 contain the
fix for this issue and work fine for me, no crashes observed.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883498
Title:
Frequent Panic in ip6_expire_frag_queue->icmpv6_send on
4.4.0-184-generic
To manage
4.4.0-185 from xenial-proposed seems stable still. Any chance of
releasing it to mainline xenial soon, we have some other needs to run
upgrades and deploying proposed packages is a bit of a hassle for a
fleet of hundreds?
--
You received this bug notification because you are a member of Ubuntu
I have deployed 4.4.0-185 from xenial-proposed to 6 VMs on Monday. No
crashes yet, so it seems to me that 4.4.0-185 is good and fixes this
issue. On 4.4.0-184 these ones crashed very frequently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can deploy 4.4.0-185 from xenial-proposed for testing on Monday. The
fix looks good, I was already staring at
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=5d41ce29e3b91ef305f88d23f72b3359de329cec
which came in 4.4.0-184.
--
You received this bug notification
Paste error in original report; the related-but-not-quite-the-same bug
was here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883498
** Attachment added: "6 dmesg of #1883498 crashes on different VMs"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883498/+attachment/5383933/+files/1883498-dmesgs-6.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I happened to do an upgrade on a number of servers last week. Some of
them got 4.4.0-179-generic and the ones upgraded a bit later during the
week got 4.4.0-184-generic as it was just released. The ones with
4.4.0-184-generic started getting stuck. With linux-crashdump
It was really meant to be helpful. You should understand this kind of bug
is truly critical. I believe this has not been the case.
I am sorry, I am not able to help in any other way for now and will not
participate in any further discussions or bug reporting.
I wish you all the best.
On Mon, 18
If there is a possibility that copy-paste will result to an error, whole
distro is useless for serious production use.
It is really sad, testing this kind of bug is so uncertain and difficult.
In my opinion programmer should be able to guarantee that such error can
not take place. Otherwise there
I updated proposed mutter 3.36.2 and tried Libreoffice Calc sheet copy -
paste, cut - paste in pretty much same way with the same pc I did at the
time I reported the bug - only few times more.
I did not run into error. I don't have any need for extensive copy - paste
activity any time soon, so
Public bug reported:
I tried to report the bug as Libreoffice bug, but they seem to ignore it as of
problem in ubuntu.
I was advised to report this for ubuntu beta 20.04.
Bugzilla Bug 132213 shows what I was able to describe at the time.
I dis some 50 cut and paste actions while working with
Hello, as I wrote in my original ticket description above, bind9
packages were not updated at this time; the crash did *not* happen on
shutdown.
However, the named process on each server crashed exactly once. There
were 0 crashes in July or August. So, I'm afraid, I can't reproduce
this.
--
You
I deployed the actual -proposed kernel 4.4.0-152.179 on 4 servers, and
it is stable for us. Previously there were multiple crashes per day.
Confirming, verification done. Thank you!
** Tags added: amd64 apport-bug apport-collected xenial
--
You received this bug notification because you are a
Public bug reported:
Ubuntu xenial 16.04, bind9 1:9.10.3.dfsg.P4-8ubuntu1.14
Yesterday the named process started crashing frequently, 49 crashes so
far on 49 different servers around the world (one crash each!). We did
run OS upgrades yesterday, but bind9 packages were not updated at this
time.
I've now got the v4 debs on 5 servers, and not a single crash since they
were installed on each. Looks good to me. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824687
Title:
Thanks, I deployed the v4 debs on one server which was particularly
unstable, and it's still up after 1 day and 8 hours now. I'll deploy
more widely on Monday and Tuesday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was experiencing this on multiple Ubuntu 18.04 servers with high UDP
workload, I219-LM Ethernet, 4.15.0-50-generic Ubuntu kernel. Many events
with "Detected Hardware Unit Hang" ... "Reset adapter unexpectedly" per
day per server. The workaround suggested by the hosting provider does
seem to
I've now got 6 crashes within past 24 hours on the #170+lp1824687v2
testing kernel on a *single* server. It's a production environment, so
I'll roll back for now. Two latest backtraces:
[ 6251.834160] Call Trace:
[ 6251.834166]
[ 6251.834174] [] skb_release_head_state+0x90/0xb0
[ 6251.834189]
Unfortunately 4.4.0-144-generic #170+lp1824687v2 testing kernel still
crashes. I have 4 hardware instances running it now, there were 2 panics
(Australia, Sweden) within 24 hours. I installed linux-crashdump on them
after the first crash to get the panic logs reliably. Attached a log
from the
Sorry for the delay. I'm back in the office now and deploying the test
kernel today to a few servers, and to additional ones tomorrow if it's
OK on the first ones.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you! I can test this on Monday, weekend is starting here in 2
minutes and this is not the greatest moment to start testing. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824687
Title:
There is the kernel.org bug ticket which describes similar oopsing
through ip6_expire_frag_queue() in 4.9 and 4.19 kernels:
https://bugzilla.kernel.org/show_bug.cgi?id=202669
I also saw crashes on 4.15.0-48-generic on a server running the same
task; I don't have stack traces to show yet since
kernel.org bug ticket, showing similar crashes on 4.9 and 4.19 kernels:
https://bugzilla.kernel.org/show_bug.cgi?id=202669
** Bug watch added: Linux Kernel Bug Tracker #202669
https://bugzilla.kernel.org/show_bug.cgi?id=202669
--
You received this bug notification because you are a member of
** Attachment added: "5 kernel stack traces of crashes on 4.4.0-145 and -146,
on 4 different hardware nodes"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+attachment/5260024/+files/hessu-ipv6_expire_frag_queue-crashes.txt
--
You received this bug notification because you are
I have had this crash, with the ip6_expire_frag_queue stack trace, more
than 18 times since 2019-04-16 on more than 10 different servers in 8
different countries. There have been some more crashes, but from these
ones the panic dump managed to go out to a remote syslog server where
it's easy to
I partly agree. Users don't bother to report the bugs as it is difficult
and as this is free software and complaining feels unjustified. However I
am simply not able to put enough effort to prove my point (will be too busy
for that now). It is incredible that basic functionality is at such a poor
Public bug reported:
When I tried to use update-manager to upgrade from 16.04 to 18.04, the
update failed due to could not calculate the upgrade.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.26
ProcVersionSignature: Ubuntu 4.4.0-140.166-generic
Public bug reported:
Logitec K800 and logitec M535 worked perfectly with Ubuntu 16.04.
I can pair the keybord alone and everything works, but mouse M535 can
not be paird at all with default bluetooth settings so that it would
work after boot. However using blueman M535 can be successfully
3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical
in our environment). It has been few days since it was supposed to be
coming and I figured that it is safe now to start installing 18.04, but
fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work.
su
Fresh install 18.04 gdm3 did succeed occasionally, but mostly froze
completely so that power button was only way out.
There was a fix that was available in proposed repository (or something)
that made things a bit different. Failure became a rule, but it was
possible to get back with
I had similar experience yesterday after installing 3.28.2 and I reported
that it does not work. But after couple of boots I have been testing every
now and then maybe some 15 times and every time it has logged in - very
slowly but success anyway. To me that is quite clear that any kind of
success
Did you test : 3.28.2-0ubuntu1.1 ?
I thought that is The version having The fix
ke 30. toukokuuta 2018 klo 18.51 KenWilson <1766...@bugs.launchpad.net>
kirjoitti:
> All,
> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password
> issue; however, it creates a new issue. As such
, looks better now.
ti 29. toukok. 2018 klo 22.47 Heikki Moisander (moisan...@gmail.com)
kirjoitti:
> heikki@ThinkPad-X301:~$ apt-cache policy gdm3
> gdm3:
> Asennettu: 3.28.2-0ubuntu1.1
> Ehdokas: 3.28.2-0ubuntu1.1
> Versiotaulukko:
> *** 3.28.2-0ubuntu1.1 500
heikki@ThinkPad-X301:~$ apt-cache policy gdm3
gdm3:
Asennettu: 3.28.2-0ubuntu1.1
Ehdokas: 3.28.2-0ubuntu1.1
Versiotaulukko:
*** 3.28.2-0ubuntu1.1 500
500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1
Mostly I don't understand this discussion and probably I should not take
part in it. There has been no progress visible to me. The bug I reported
was assigned as duplicate to this, so if this is now fixed, should I report
the bug again?
Anyhow it appears to me, that to ordinary users sharing the
2018-05-18 17:05 2018-05-18 14:05 UTC Crash gnome-session-bin
link:
https://errors.ubuntu.com/oops/d6ec2448-5aa9-11e8-8106-fa163ef911dc
ma 21. toukok. 2018 klo 10.11 Daniel van Vugt (daniel.van.v...@canonical.com)
kirjoitti:
> Bug 1766137 is not fixed in 18.04 yet. Only in 18.10. So it may
I did run "ubuntu-bug
/var/crash/_usr_lib_gnome-session_gnome-session-check-accelerated.120.crash"
Looked like it was sent.
This bug shows up differently copared to 1766137. This time login will not
progress to blank screen and probability is 100% now as bug 1766137 showed
up to me only maybe
Public bug reported:
While trying to change to another user account without boot display
manager freeze. ctr-alt-F2 return back to previous user. While trying to
log in to another user account after log out from another result to same
immediate freeze. ctr-alt-del boots and after this login
Really sorry about spamming, but I only now figured out how to get output
from relevenant time ( I hope)
getUniqueBusNameSync@
/usr/share/gnome-shell/extensions/
ubuntu-appindicat...@ubuntu.com/util.js:58:20
org.gnome.Shell.desktop[1812]: #3
0x730315f0
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4
0x561a8f6df7a0
pe 18. toukok. 2018 klo 21.01 Heikki Moisander (moisan...@gmail.com)
kirjoitti:
> Not sure what came out but this is out come of running journalctl right
> after b
Not sure what came out but this is out come of running journalctl right
after booting after freeze.
I need clear guidance to get something else more relevant.
Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33
EE
huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version
I installed proposed updates. Now it freeze a bit earlier and even more
often. Login screen remain visible and no cursor movement while before in
looked like progressing with blank screen with cursor movement until final
freeze.
pe 18. toukok. 2018 klo 19.20 KenWilson (1766...@bugs.launchpad.net)
Work around does not work for. It is not about nvidia driver. Lets face
it, it is a showstopper for ubuntu 18.04 until bug is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
Public bug reported:
Login works on start up, but when logged out and login in with another
user end up blank screen with only moving cursor. Will not make any
difference using xorg or wayland. It is failing some 15 times out of 20
tryout. Sometimes it boots by itself sometime ctrl+alt+del seem
If I log out and log in as a different user I get blank screen with mouse
cursos visible and movable, but nothing else. If I log in as same user it works
or if I boot I can log in with any user.
18.04 normal set up. I did install and purge gnome-session (to test "vanilla
gnome").
As a fix I
works with 20180425 release
** Changed in: ubiquity (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/1766796
Title:
Installer crashes in update-grub Bionic
Public bug reported:
Installer crashes at update-grub, while installing in system running
from USB
Linux kubuntu 4.15.0-19-generic #20-Ubuntu SMP Sun Apr 22 00:03:34 UTC 2018
x86_64 x86_6
Bionic Beaver_ - Release amd64 (20180424)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity
** Changed in: debconf (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/bugs/1693540
Title:
package linux-image-4.8.0-53-generic (not installed) failed
I am currently getting these on 4.4.0-66, on 14.04LTS / trusty. Xen VM.
Unfortunately unable to migrate immediately to 16.04LTS (largish
platform with many custom packages built for the distribution). On the
3.13.0 kernels I don't get these, but would like to go to 4.4 due to
other fixes being
Public bug reported:
Description:Ubuntu 14.04.5 LTS
Release:14.04
heikki@heikki-Aspire-M5201:~$
apt-cache policy pkgname (cant find pkgname)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.9
ProcVersionSignature: Ubuntu 3.13.0-107.154
On the other hand, turning off scatter gather caused a rather constant
0.1% packet loss (transmit drops) in my setup (trusty on Xen). VPN
gateways, with NAT and firewalling, relatively high throughput at times.
Enabling scatter gather removes the constant small packet loss but then
I do get the
Since yesterday morning I've had 3.13.0-46.75 running on 6 VMs. Those
VMs haven't had any xen_netfront: xennet: skb rides the rocket
messages. Meanwhile, 8 other VMs with 3.13.0-44 did have these errors.
So, looks good to me. Not absolute proof, but looks good.
--
You received this bug
Installed 3.13.0-46.75 on 6 VMs which exhibited this problem daily. I'll
confirm tomorrow evening, if it's gone away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317811
Title:
Dropped packets on
I am sorry, I fail to understand the discussion going on - have not been
reading it too carefully though. Why this still continues? I think it is
quite clear to development team that fix is needed and I am 100% certain
they know how to proceed. It is just matter of prioritization, which brings
me
We don't need java right now - so no hurry for me with the fix or
workaround. Thanks anyway to all.
2014-11-02 12:21 GMT+02:00 Paul Dooley 1363...@bugs.launchpad.net:
Remember when using the workaround in post #14 to change amd64 to
i386 if you are using a 32-bit installation...did this and
not solve easily.
br Heikki
2014-11-01 15:49 GMT+02:00 Bob H 1387...@bugs.launchpad.net:
you have not installed incorrectly
there does appear to be a problem with icedtea-netx:amd64 1.5.1-1ubuntu1
in the repositories at Utopic
This means that icedtea-web cannot be installed on Utopic until
Public bug reported:
Sorry, not able to add much comment - this report is originated
automatically
I tried to install java support when I needed it in the middle of
session in certain www site. As I was logged in to service requiring
relatively demanding authentication using keys provided
I tried to install it several times again after completely removing
everything java related using instructions in
http://askubuntu.com/questions/84483/how-to-completely-uninstall-java
then tried to install icedtea from sw-center.
--
You received this bug notification because you are a member
This bug really seems to be random. My version of this bug really did disappear
a month ago with description I gave earlier. I promise to you if this bug ever
comes back to me I will do my best to nail it for good! It was really annoying.
1306550 Never forget!
--
You received this bug
Is it possible that this bug is originating from Unity Tweak Tool
Switcher tab?
It seems that only thing I need to do to reproduce this bug is to tab
into Show Desktop back and forth from full screen Firefox and cursor
is misplaced. And at least one way to fix it is to disable/enable
Switch
I was searching this bug with keywords cursor wrong position.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306550
Title:
Wrong mouse-coordinates in the window after minimize/maximize of after
When I close laptop lid, machine hibernates. But when I open the lid
maybe an hour later and give a password screen lock asks, I can remove
lock but screen turns blank. I guess screen lock doesn't tell to the
powermanager that it should turn screen from blank state to showing
desktop. If I remove
After complete system reinstall, and selecting fglrx from Driver Manager
(instead of manually installing from http://support.amd.com/en-
us/download/desktop?os=Linux%20x86_64) I have no problems. No need for
manual install.
Still keyword search in gnu-manager SHOULD search label Driver from
Public bug reported:
This is a bug report against gpu-manager.c in ubuntu-drivers-common.
~/Documents/VC/ubu/ubuntu-drivers-common/share/hybrid$ bzr log
revno: 56
tags: 1:0.2.91.1
author: Alberto Milone
committer: Package Import Robot
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1299002/+attachment/4048600/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299002
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1299002/+attachment/4048601/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299002
apport information
** Attachment added: UbuntuDriversDebug.txt
https://bugs.launchpad.net/bugs/1299002/+attachment/4048602/+files/UbuntuDriversDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For the first time, the corruption is now in both screens
simultaneously.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280969
Title:
Corrupt mouse cursor when using multiple monitors
To manage
Video and photos of the thing. Screen and video capture shows perfect pointer.
However on the screen pointer is corrupt.
Simultaneous screen capture and video (with camera) provided. Does this isolate
the bug at all?
https://www.dropbox.com/sh/cbk67l0wxg3zbzo/Pg9tUVM6n3
--
You received this
Screen capture of the window taken when mouse pointer corruption is
visible on the screen. Screen capture suprisingly shows that everything
is fine. Mouse pointer here is as it should be. However the photo of the
previous comment was taken at the same time, without moving the mouse
and clearly in
I have reproduced the same on Ubuntu 13.10 (KDE), Linuxmint 16 (KDE),
and now also Linuxmint 16 (Cinnamon).
I will attach screenshot (using camera, where you can see the actual
phenomenon), Screen capture DOES NOT capture the error, I will attach
that to next comment. Maybe that helps to isolate
** Attachment added: Photo of the screen capture taken at the same time as
previous photo
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1280969/+attachment/3983473/+files/Screenshot%20from%202014-02-16%2016%3A16%3A13.png
--
You received this bug notification because you are a member
Public bug reported:
I have two screens, and sometimes on one of the screens mouse cursor
gets corrupted. So far always vertically in 5 slices. The corrupt cursor
is always in the primary screen. The cursor is fine on the second
screen. If I take a screenshot (using the screenshot application on
** Changed in: language-pack-fi (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859232
Title:
Evolutionin yhteystietoja siirtäessä siirry yhteystieto,
Hi,
just to add that I have the same problem with Elo TouchSystems 2515
IntelliTouch Plus USB Touchmonitor. When running xinput list-props
options are correctly listed, but they do not take effect.
Running 12.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs,
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1000362
Title:
package winbind 2:3.6.3-2ubuntu2.1 failed to install/upgrade:
aliprosessi installed post-installation script palautti
Public bug reported:
Failed update to ubuntu 12.04
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: winbind 2:3.6.3-2ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
Uname: Linux 3.0.0-20-generic i686
ApportVersion: 2.0.1-0ubuntu7
AptOrdering: winbind: Configure
Public bug reported:
Failed update to ubuntu 12.04
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: winbind 2:3.6.3-2ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
Uname: Linux 3.0.0-20-generic i686
ApportVersion: 2.0.1-0ubuntu7
AptOrdering: winbind: Configure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000362
Title:
package winbind 2:3.6.3-2ubuntu2.1 failed to install/upgrade:
aliprosessi installed post-installation script palautti
virhetilakoodin
*** This bug is a duplicate of bug 768184 ***
https://bugs.launchpad.net/bugs/768184
This thing seems to appear when I leave the PC idle for a long time.
Power saving options do not seem to affect like they are being set, but
I really don't know very well what is the fact.
--
You received
Hi. I can reproduce it always. Gwibber version is 3.3.2 as mentioned in
the bug report.
For example connecting to Facebook gives me only error:
Cannot connect to destination (graph.facebook.com)
I added some traces to the gwibber python code and it seems to load
libproxy correctly but for some
I just installed 12.04 beta2 amd64 to Fit-pc3. Installation was file, I
just selected the use the whole disk -option. Boot after installation
was fine. I took all the updates - reboot - does not boot anymore.
Fit-pc3 bios version: BZ_2.1.0.333_5 X64
Booting leads to EFI Shell version 2.0.0
ver
I made a reinstallation from the same installation media (12.02 beta
amd64 USB-stick made with UNetbootin) and again using the whole HD. When
I took all updates after installation, I noticed there were fewer
packages to upgrade: 498 vs 503 before. This matches to the 5 packages
listed in the bug
I switched to 64-bit installation and for me there seems to be no
difference to 32-bit:
* fresh up to date 64 bit 12.04 beta2
* installation of FGLRX closed source driver from system settings
* installing packages: vainfo, xvba-va-driver, libva-egl1, libva-glx1
$ cd
I have a 32-bit installation, but had the same problem. It tries to
open:
libva: Trying to open /usr/lib/i386-linux-gnu/dri/fglrx_drv_video.so
but there was no such file in that directory.
However I found the is two files in the system:
/usr/lib/dri/fglrx_drv_video.so
Same problem here. I got the valgrind working with some real stupid hack
but not sure what it breaks. Here are the steps:
1. Move from /usr/lib/debug/ the following directories to the following places:
usr/bin/ - usr/bintmp/
usr/lib/ - usr/libtmp/
usr/sbin/ - usr/sbintmp/
sbin/ -
Public bug reported:
After trying to authorize either twitter or facebook with Gwibber I get
error messages that the destination is unreachable after long time
waiting for authorization page to open. I am behind proxy and other
protocols (ssh/http/https) are running ok through the proxy. I am
** Attachment added: gwibber log
https://bugs.launchpad.net/bugs/956865/+attachment/2880338/+files/gwibber_log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956865
Title:
Cannot connect to
Public bug reported:
I have two displays on my Ubuntu 10.04 LTS system, ATI Radeon RV620 LE,
configured as individual screens (no xinerama). One is new and wide-
screen, 1920x1200, and the other is older, running in 1600x1200.
When I move the mouse cursor over the right edge of the left
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871665
Title:
Mouse pointer does not move correctly from a screen to another in a
dual-head config - jumps too far
To manage notifications about this
I can confirm that Timo's new libvoikko 3.1-1ubuntu1 fixes this bug in
Natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832582
Title:
mozvoikko makes Firefox 6 crash
To manage notifications
Chris: did I miss something, where should I find the unstripped build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832582
Title:
mozvoikko makes Firefox 6 crash
To manage notifications about
Ok, I'll test it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832582
Title:
mozvoikko makes Firefox 6 crash
To manage notifications about this bug go to:
I can confirm this. FF doesn't crash always, but sometimes when one
opens a page containing a textbox (= Firefox tries to check the
spelling in it using Mozvoikko) it crashes.
Crash report: https://crash-
stats.mozilla.com/report/index/4d70e202-2737-4eb7-a9a4-0da282110824
I tried to install
** Attachment added: Hopely uncorrupted logs
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/582241/+attachment/2237220/+files/dist-upgrade.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Using a VIA cpuchipset based computer. VLC and mplayer both crash when
video starts playing. I took the edge drivers but did not see much
improvement (now I seem to get few video frames before crash). Going to
full screen mode triggers it immediately, window video shows
** Attachment added: X log from the crash
https://bugs.launchpad.net/bugs/805477/+attachment/2190572/+files/Xorg.1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805477
Title:
Xorg crash
To
1 - 100 of 337 matches
Mail list logo
