Public bug reported:
Binary package hint: rhythmbox
I just downloaded this player from ubuntu's list of selections.
Originally, it was indicated by the Synaptic Package Manager that
Rhythmbox was among the preloaded ubuntu applications, but the icon was
not to be found that would start the applic
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/17253291/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/17253293/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/17253294/ProcStatus.txt
--
radio
Just installed a fresh copy of Xubuntu 14.04.1 and I also have that
problem. In addition after wakeup the screen stays black after the
password dialog. I don't mind, because I wouldn't want to go into sleep
mode anyways. So I hope this can be fixed properly any time soon.
"This is a MAJOR inconven
I continue to see this problem on a daily basis, often after a resume
from suspend, I am not running Wayland, and this crashes my
gnome-session half the time, so something there is some confusion/bug
somewhere. This morning's crash resulted in message from xorg-server so
I let apport file a bug ag
Public bug reported:
This file disappeared from 19.10 dev package. Without the *.la file,
libtool fails to configure libraries with GTK dependencies.
My work around was to grab the file from 18.04 and change the metadata
for the current library versions. That allowed me to successfully
compile
Public bug reported:
Description:Ubuntu 18.04 LTS
Release:18.04
nvvp should run without crashing. Other tools in the toolkit are
working.
Error message is:
Xlib: extension "RANDR" missing on display ":1.0".
WARNING: An illegal reflective access operation has occurred
WARNING: Ille
Thank you very kindly for the quick reply. That worked perfectly!
It appears that openjdk-11 is installed by default.
On 04/25/2018 03:46 PM, Graham Inggs wrote:
> sudo apt install openjdk8-jre
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039
--
You received this bug notification
BTW, if i might make another comment rather than file a new bug report:
nvprof requires root privs. Even suid/guid root is not enough.
On 04/25/2018 03:46 PM, Graham Inggs wrote:
> sudo apt install openjdk8-jre
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039
--
You received this b
Public bug reported:
Description:Ubuntu 18.04 LTS
Release:18.04
Expected behavior: profile output
Actual behavior: error messages
Reproduce as follows:
cd NVIDIA_CUDA-9.1_Samples/0_Simple/matrixMul
nvcc -I ../../common/inc matrixMul.cu -o matrixMul
# check the exe works
./matrixM
There is no change running 'nvprof' immediately after 'sudo 'nvprof' or
vice versa. The former fails, the latter works. The same is true for
'nvvp' because of course 'nvvp' calls 'nvprof'. I ran 'nvprof' with
strace to look for some sort of write access to a /proc or /sys resource
but I didn't s
Thanks. Did that, but no change in the 'nvprof' behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767205
Title:
nvprof does not complete without sudo
To manage notifications about this bug
I tried it, and the behavior is the same.
However, the thread http://devtalk.nvidia.com/default/topic/1025155
/-resolved-profiling-error-4168-999 suggests that this issue may be an
upstream bug, although the developer did not give details.
So maybe the Ubuntu package is all good, but we'll need t
Same problem with bandwidthTest. nvprof works with deviceQuery and
reports time spent in the various cuda query calls, but also reports "no
kernels profiled".
I did check the /dev/nvidia* permissions and they look fine to me, e.g.
crw-rw-rw. As I also mentioned, suid/guid on nvprof did not help
Public bug reported:
I have cryptoswap set up both with the 2 GB default swap file and an 8
GB swap partition with 8 GB of ram. However, the system does not use
this swap when it should. For example, if I run a little test code
which attempts to allocate 10 GB of memory in 1 GB chuncks, the syst
The code that I used to force failure, memtest.c, is attached to the bug
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762468
Title:
Cryptoswap not working in Bionic
To manage notification
It seems that cryptswap is working correctly on 17.10 with the kernel
4.13.0-36-generic on a different machine using the same test as
described above. I tried the same kernel (4.13.0-36) on 18.04 (machine
used in original post) and it still fails. Of course, I checked that
the swap appears in /pr
Yes, the problem does occur in mainline 4.16 and I have added the
requested tag.
If anything, 4.16.1 seems slower than 4.15 release kernel even for no
cryptswap. It could be that my disk is too slow for cryptswap, but it
did work in 17.10.
The obvious work around is not to use cryptswap, of cour
The first kernel on that list that exhibits the bug is the first one:
4.14 Final. Recall: the bug results in a full up hang. The disk stops
swapping (it's audible). I can reboot with sysctl SUB however.
I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
4.11.12-041112-generi
BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy.
On 04/11/2018 05:51 PM, Martin Weinberg wrote:
> The first kernel on that list that exhibits the bug is the first one:
> 4.14 Final. Recall: the bug results in a full up hang. The disk stop
In response to #7, I don't think this is the same issue. The cryptswap
initiates with no difficulties, timeouts, etc. on boot. When I first
installed Bionic, ubiquity did not correctly install the swap, and I
filed #1759253 on that issue.
--
You received this bug notification because you are a
Some good and bad news: I have been testing this in a running Gnome 3
environment. I decided to start testing on console. On console, all
kernels seem to fail using crypt swap. This suggests to me that failure
must depend on current memory usage, dirty ratio, or some such runtime
condition.
How
Emiliano: the problem file is
'/etc/X11/Xsession.d/50_check_unity_support'. You might want to confirm
that this is gone with the purge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
Title:
I'm not an expert, but you might want to see if you can gain some
insight from the output of 'journalctl -b0'.
E.g. is your system using the framebuffer driver "fbcon: xxx" or "[drm]
..." during boot up?
In the 'journalctl -b0' output I posted above,you can see that it's
using the frame buffer.
Emiliano: I'm grabbing at straws, but try checking for other files in
'/etc/X11/Xsession.d/' that might be setting 'export
LIBGL_ALWAYS_SOFTWARE=1' in the environment. E.g. 'grep -H LIBGL
/etc/X11/Xsession.d/*'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Well, this sounds like a different problem. The problem I reported was
very clearly the result of an incomplete package upgrade/removal
resulting in a failed test for unity compatibility leading to setting
that environment variable for software gl.
You might consider opening an new bug report wit
P.S. I also note that you are using wayland. No reason to think it will
matter, but just of of curiosity, have you tried the xorg session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
Title:
I look a quick look at your posted data. It does seem odd that your
system starts out configuring the drm and then uses fb. Do you have
anything custom on your boot line, like some video parameters? E.g.
'cat /proc/cmdline'. More grabbing at straws.
--
You received this bug notification becau
Yes, I would make a new comment to your bug report with the logs under
xorg session. I hope that one of the Ubuntu developers have a clue
about this. I'm curious myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
After a recent install of the 18.04 (why is a separate story), I notice
that after some number of successful screen locks, I become locked out
of the desktop with an authentication failure. During those
unsuccessful attempts to log in, syslog shows:
Mar 13 22:46:04 magpie /u
Addendum: I was running the Xorg ("Ubuntu") session when the problems
occurred. I'm trying the Wayland session now, so the autogenerated tag
is not correct, and maybe not relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Also a problem with the Wayland session. Not a big surprise. For now,
I've turn off the screen lock.
Not sure what else to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greete
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greeter/lockscreen fails to authenicate in an endless loop
To manage notifications about this bug go to
Daniel,
I took a few days, but it did again fail with the same issue. I'm
attaching the log, collected shortly after the failure by switch to
console while running the Wayland session, as you requested. Had to
reboot afterwards, to be able to log on to the desktop.
Hope this helps you spot the
Thanks. That variety script was from an old version of variety, it
seems. I removed that and checked that the current scripts in
/usr/share/variety/scripts do not have that bug (looked like an
operation on a shell variable that may not exist). I did notice a few
variety crashes, but they do not
I'm still getting failures. This is with a fixed variety and no gnome-
shell extensions other than the default ubuntu extensions.
I don't see but reports similar to this, so I gather that others are not
generally plagued by this problem. Nonetheless, I appreciate any advice
or comment you have o
I saw that. But the disk is far from full. Don't know what's up with
the /snap loopback devices. The hard drive itself is at 35%. Here's
the df output:
Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 767M 1
Thanks. Your comments led me to look at swap. There is no swap!
I installed from iso image several weeks ago (I am traveling and had a
bad ecryptfs corruption, not sure how this happened, and needed to
reinstall, and had this on my memory stick for testing).
I selected encrypted and had an prex
I've been studying the swap mess. It seems that the installer made a
swapfile called /swapfile and entered the line in /etc/crypttab as:
cryptswap1 /target/swapfile /dev/urandom swap,offset=1024,cipher=aes-
xts-plain64
which is the wrong, non-existent filename. So that seems to be an issue with
Public bug reported:
I needed to do an 'emergency' reinstall while travelling owing to a
hopeless corrupted encryptfs. I happened to have a Bionic iso from
March 11 and used that to install to my laptop.
Soon after installing, I noticed various problems with logins, hangs,
etc. which I recently
** Attachment added: "/var/log/installer/partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1759253/+attachment/5092157/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
animations were gone. After some digging, it seems that gnome-session
incorrectly assumes that my graphics has no acceleration, when in fact
it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated gra
** Summary changed:
- No acceleration after upgrading to 18:04 gnome-session-check-accelerated
incorrectly picks llvmpipe
+ No acceleration after upgrading to 18.04: gnome-session-check-accelerated
incorrectly picks llvmpipe
--
You received this bug notification because you are a member of Ubu
I have figured out the problem: the installer removed nux-tools, left
over from unity, but did not purge it. This left a start up script in
/etc/X11/Xsession.d which interfered with gnome. Purged that and the
problem was gone.
So this is a dependency bug in the nux-tools package (or perhaps some
Public bug reported:
There seems to be a cycle of dependencies that breaks upgrade path.
However, the current 18.04 has no broken packages, is upgraded, and
works correctly. I was unable to spot the problem in the log.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader
Public bug reported:
The attempt to upgrade generates cycles of broken dependencies, even
though the initial 18.04 system has no broken packages, is upgraded, and
is working correctly. The upgrade logs did not give me a clue; maybe
it is something simple?
ProblemType: Bug
DistroRelease: Ubuntu
** Attachment added: "syslog surrounding the dead hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387971/+files/syslog.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "kern.log containing a dead hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387972/+files/kern.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I ran it until it happened again. I'm attaching the syslog and
kern.log from the time of the crash, which was Jun 28 at about 15:30.
Doesn't seem to be a lot to go on here . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
This seems to be the same problem reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
** Bug watch added: Red Hat Bugzilla #1506339
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
This issue has been a persistent but infrequent problem for many years
with the T440s. It only occurs when the laptop is docked. I have
reported this bug several times. However, with the current kernel
release, 5.4.0-37, this occurs at least once a day. The kern.log lines
This kernel also shows continuous rendering artifact on the native LCD
screen, such as the windows underneath the current active window appear
as flickering ghosts. No problems on the previous released kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The obvious work around is to make the link by hand, which I did, and
all is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869612
Title:
libmpi.so link is missing
To manage notifications abo
Also note: this was an upgrade from 19.10, not a new install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869612
Title:
libmpi.so link is missing
To manage notifications about this bug go to:
ht
I tried Wayland, too, same problem.
My workaround was to remove the Ubuntu package and compile Paraview from
scratch by cloning the git master branch. It takes some time, but it
works. Follow the instructions here:
https://www.paraview.org/Wiki/ParaView:Build_And_Install
--
You received this
If you want to try that, you can grab a more recent kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I doubt that this
will fix your issue. I'd bet on a configuration thing, but not sure
what. You don't, by any chance, have a custom xorg.conf (in /etc/X11
or /usr/share/X11)? I thin
xorg.conf has been replaced by the rules in /usr/share/X11/xorg.conf.d.
You can see if there is some older cruft in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
Title:
No acceleratio
Sebastien: Yes, that is precisely the issue! Took me an afternoon of
sleuthing to figure it out.
Emiliano: You might want to find out if any package is providing that
file (e.g. dpkg -S 20-intel-graphics.conf) and delete that file if it
turns out to be orphaned. I do not that file, but I do have
We can close this bug report at this point. But I do appreciate the
follow up!
It turns out that there were two problems. The first was that 18.04 had
misconfigured the cryptoswap so that was not working at all. I reported
this separately before the release of bionic and I believe that this bug
I refiled the bug at bugzilla.gnome.org as bug 790040.
The link is: https://bugzilla.gnome.org/show_bug.cgi?id=790040
I'm really surprised that there are not more complaints about this. To
be fair, the dock+external monitor setup has NOT worked perfectly in any
release Ubuntu release, including
The symptoms and behavior are nearly the same, so the issue seems
closely related, if not the same. However, the report is for different
hardware and dock (UltraDock rather than OneLink dock although both
Haswell). But, without doing the back port of Dave Airlie's patches to
4.9.x, 4.10.x or 4.4.
Public bug reported:
When using with dock, attached monitor is not detected, laptop monitor
remains blank. Requires a reboot
4.4.0-59 works fine. I'm guessing this is due to the i915 patches for
DP.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-generic 4.4.0-62.83
Also, and not sure if this is related, Plymouth does not correctly
render the splashscreen on boot up. Part way through, the screen blanks
and only the "dot icons" are visible. Again, this does not occur for
earlier kernels.
--
You received this bug notification because you are a member of Ubun
Another thought: I'm using the modesetting driver, not the intel driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662381
Title:
linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock
T
I am happy to report that linux-image-4.4.0-63-generic from xenial-
proposed _is_ working correctly with the T440s on and off the dock. So
the bug is gone from the -proposed kernel package.
Thanks for that!
If we could only get the DP audio to work on the dock, sigh. It hasn't
worked since Kern
Public bug reported:
In the default configuration, resuming my T440s on the Lenovo ultradock
results in not detecting the external monitor followed by a suspend.
If I open the lid while on the dock, gnome detects the external monitor
and blanks the laptop display. Then, closing the lid results i
Just to make sure, I again repeated the sequence of events outlined
above on the stock 17.10 kernel:
Linux magpie 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
The behavior is identical to that reported above.
One minor elaboration: when I open the
Yes, GNOME on Wayland. I will try GNOME on X.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725698
Title:
Size decreases when cycling between full-screen mode using F11
To manage notifications ab
Yes, no problem with GNOME on Xorg. Thanks for the heads up.
I found another problem with Wayland handling the dock + laptop lid that
works correctly with Xorg. Just trying to help. Not sure what package
to file a bug on, do you? Would that be xwayland?
--
You received this bug notification
Public bug reported:
I have a Lenovo T440s (haswell) and an ultradock with external monitor.
If I resume on the dock, wayland seems to recognize the lid as closed
and suspends. The work around is to (1) open the lid, bring up the
display control tab and switch to single monitor, choose the extern
Public bug reported:
Launch an gnome-terminal and cycle between full screen and normal by
pressing F11 twice. The original size of the terminal is not restored.
Doing this multiple times, the window continues to shrink.
This did not occur on 17.04 or earlier. I use this regularly as part of
my
Public bug reported:
After resuming from a suspend, the previous behavior was to reconnect to
the owncloud server. Or, instruct the app to reconnect.
With 16.04, the app claims that there is no connection to the owncloud
url. Trying to log out of the server seems to force confuse the app (it
th
I see that this appears to be the same as bug #1572321.
Sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580632
Title:
server connection state is confused and/or lost after suspend
*** This bug is a duplicate of bug 1572321 ***
https://bugs.launchpad.net/bugs/1572321
** This bug has been marked a duplicate of bug 1572321
owncloud network access is disabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot
be chosen as a sink. This is only a problem with the dock; audio works
when plugging HDMI through the laptop's DP input.
The audio did work with the dock in Ubuntu 14.04. Did something in jack
detection
Does this issue have to do with MST support in kernel 4.4? The 3.13 in
14.04 did not have MST support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582414
Title:
No HDMI audio on Lenovo pro dock
Since this is a QT bug in the Ubuntu distribution, what is the correct
procedure for requesting (begging?) the QT maintainers to backport the
patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157232
The proposed package fixed the bug. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573639
Title:
ownCloud Client system tray icon integration broken
To manage notifications about this bug
Thanks Luke.
I tried it but, sorry to report, the results are the same: pavucontrol
claims that the HDMI is unplugged.
I also checked with "aplay -D" commands and none of the HDMI devices
detected will play. The internal audio and a USB device are detected
and work fine.
--
You received this b
Thanks.
Booted with the latest daily, which is kernel 4.4.0, and it does not
detect HDMI/DisplayPort on the ThinkPad ultra dock.
Also, from the old-releases repo, I downloaded the 14.04.1 iso running
kernel 3.13.0-32, and that one DOES detect the HDMI/DisplayPort.
--
You received this bug notif
I also tried 14.04.2, which is kernel 3.16.0-30, and that also detected
the HDMI/DP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582414
Title:
No HDMI audio on Lenovo pro dock with T440s
To mana
Public bug reported:
The application works, but the indicator is a nice feature. The
workaround is minimize and maximize the GUI instance manually.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: owncloud-client 2.1.1+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Una
I saw a few changes for glib-networking pushed today. However,
owncloud-client doesn't depend on these. But just to confirm one way or
the other, I upgraded and rebooted. I can report the same broken
behavior as in the original post.
Henry: can you be more specific? What packages did you updat
Thank you for that extra info, Henry!
So, with a minor bit of sleuthing, I figured out that you are using the
opensuse repository rather than 'universe' for your owncloud-client. I
was hoping to stick to the Ubuntu-maintained repository for consistency.
However, I can confirm that the owncloud-c
Public bug reported:
Audio works on internal speakers and headphones using card 1 (HDA Intel
PCH). But pavucontrol will let me choose HDMI even though it appears
under "aplay -l" and under /proc/asound things look ok to me.
Also note: this is a laptop on a Thinkpad Ultradock with the HDMI
plugg
I meant to say: pavucontrol will NOT let me choose HDMI as output.
Sounds can not be routed to HDMI. I tried "aplay -D some_sound.wav" for
all channels in the "aplay -l" list. Only PCH works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
This behavior began with upgrade to 12.04, no problems in 11.10.
strace reveals that the cpu is consumed by continuous polling.
Putting thunderbird "offline" stops the polling.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 11.0.1+build1-0ubuntu2
ProcVers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992326
Title:
Thunderbird polls continuously, using an entire core
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
More info:
I disabled the global indexing and the enless spinning stopped.
I then removed the global index sqlite databases, restarted thunderbird
and re-enabled the global indexing.
After rebuilding the index, all was well.
So in the end, I'm not sure if this was an event (i.e. corrupted
datab
I've been having the same problem. But only on one of my machines. So,
on a hunch, I quit thunderbird, deleted the global-messages-db.sqlite,
relaunched thunderbird and let it reindex from scratch. After some
minutes, the indexing was finished and the cpu usage by thunderbird
returned to zer
On 05/23/2012 04:20 PM, Michael Nagel wrote:
> Martin, can you give more detailed information about how to stop
> indexing and how to remove the sqlite databases so that I can check
> easily if this affects me too?
>
Hi,
Sorry, I've been traveling.
Go to: Edit->Preferences->Advanced and toggle o
Public bug reported:
No wallpaper is displayed after update to 13.04 from 12.10. I tried
making a new user (to get a fresh configuration) and the behavior is the
same. I can not change to a solid background either. Oddly, the
background _does_ appear on the lock screen.
I also note that loggin
I'm testing this patch against the default 13.04 kernel
(3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013 x86_64
x86_64 x86_64) now.
So far so good . . . will report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
No, I'm sorry to report that the
358466cb1596bb001f8050ea84fdbbd9bfdd69c1 does not really help. After
using the patched i915 module "normally" I tortured it with three
glxgears and youtube in HD mode. This hangs it within a few minutes.
Doing the same test with 3.10.0-997-generic from kernel-ppa
Thanks for the hint. I tried the 3.8.13 kernel on x86_64 with a Lenovo
X220.
I can still torture out hangchecks with 3.8.13-03081302-generic #201306071405
SMP Fri Jun 7 18:06:32 UTC 2013 x86_64
by running three glxgears and youtube at HD resolution, e.g.:
[ 787.335798] [drm:i915_hangcheck_hung
Public bug reported:
This report is related to a number of i915 GPU hang reports since kernel
3.8.x. The DRM in the official kernel hangs so often that it is
unusble.
The hang is easily reproduced by pushing the rendering system very hard.
E.g. I can always make the hang within a few minutes by
Try a more recent kernel from the ppa mainline. I am currently using
raring with Kernel 3.9.8 with good success. Kernels 3.8.x were
producing hangchecks requiring window restarting regularly on a
sandybridge based laptop. However, with the latest 3.9 or 3.10, the
occasional hangcheck recovers wit
Matze:
Try using 3.9.8 not 3.9.0-rc8. I had very poor success with 3.9.0-rcX;
it was no better than 3.8.X.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140716
Title:
[regression] 3.5.0-26-generi
Install the saucy version from mainline; I found no packing or
dependency issues under raring, even for the daily builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140716
Title:
[regression] 3.
That is correct. The default raring kernel will be very disappointing
for people that are experiencing the problems outlined in this thread.
It seems that only >3.9.7 has a usable kernel for affected Sandybridge
users (I am using a Lenovo X220). Even then, the bug remains at some
level but it mo
Public bug reported:
These GPU hangs seem to occur when using firefox along with other
applications. Although it is not reproducible, or at least, I have not
been able to find a recipe for introducing it.
In this case, the GPU recovered. In many cases it does not.
The relevant lines from the s
1 - 100 of 126 matches
Mail list logo
