Public bug reported:
While using Gnumeric, I experienced the following: If you add a data
filter to a column (Data - Filter), and then click on the little arrow
in the top cell to display all the values you can filter for, all other
areas of the screen become unresponsive to any mouse clicks, the
I am not sure if attributing this problem to gnumeric is helpful here.
Fixing Gnumeric to make a click outside of the drop-down list result in the
same behaviour as pressing the Escape key would easily break reproducibility of
this problem, but it would not fix the underlying problem with the
apport information
** Tags added: apport-collected oneiric running-unity
** Description changed:
While using Gnumeric, I experienced the following: If you add a data
filter to a column (Data - Filter), and then click on the little arrow
in the top cell to display all the values you can
Thanks for the instructions. I did as you said.
By the way, I tried to use 'ubuntu-bug' originally, but it wouldn't let me
submit a bug without specifying the package. As I said, I do not think that
this bug should be fixed in the Gnumeric package, but I don't know in which
package the
Christopher M. Penalver, as I've been saying from the beginning, I couldn't
care less whether this behaviour is changed in Gnumeric or not. In my opinion
it is a bug in Ubuntu (the window manager?), as no program should be able to
grab possession of the whole desktop and the keyboard including
Using 0.10 on Dell Latitude E6320 with Ubuntu 11.04 x64. Touchpad recognised
correctly and I can mange it using the Mouse or the Pointing Devices
settings. A few things I noticed:
- Whenever I reboot, the touchpad is unresponsive and I have to turn it off and
on again in Pointing Devices before
*** This bug is a duplicate of bug 550625 ***
https://bugs.launchpad.net/bugs/550625
Until someone changes the title of #550625 to reflect that it includes cases
where the Alps touchpad is NOT recognised at all, I do not see how this can be
a duplicate. I have seen #550625 before, but I
*** This bug is a duplicate of bug 550625 ***
https://bugs.launchpad.net/bugs/550625
OK, just to confirm,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/comments/492
solved it for me, and my Alps touchpad is now recognised AND seems to
work correctly. Great work by Seth!
--
You
Great work, Seth! I've been following
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/760142, as my Alps
touchpad was not recognised at all, so I thought that this was a different
problem. I applied your patch out of curiosity and now my Alps touchpad is
recognised correctly and works.
This is Ubuntu 11.04, with 2.6.38-11-generic on a Dell Latitude E6320
and I am still seeing this issue. My external monitor (DVI through a
docking station) stays off during reboot or resume, sometimes with the
login screen not visible so that I have to type in the password blindly.
After login, it
Same issue here on Dell Latitude E6320. Scrolling on the side works, but
there is no way to access/change touchpad settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784965
Title:
Touchpad
gvfs crashed on me on Ubuntu 11.04 while removing apport in the Software
Center. No idea if this was related. Don't even know what gvfs does...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/638313
I am having the same issue on my Dell Latitude E6320 and 2.6.38-11-generic
kernel, and it is very reliable now. Every time I want to reboot, the screen
goes blank and nothing happens. Do search for some relevant log messages, I did
it step by step: 15:14 requested reboot, 15:21: forced shut
Jim, thanks for that, works perfectly on my Dell Latitude E6320. I'll
add the script to my startup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760142
Title:
Several Ubuntu-certified Dell
They may be related, but the description of 550625 seem to focus on the
loss of scroll support, while this here is about the false recognition
of the touchpad as a mouse. On my Dell Latitude E6320, for example,
scrolling works, but there is on way I can change any of the touchpad
settings due to
I have a very similar configuration to jlgoolsbe and yet the gpointing-
device-settings settings are not persistent on my Dell Studio.
TwoFingerScroll is greyed out in the gnome settings, but I can activate
it in gpointing-device-settings and then it works. However, after every
Same here, just had a crash again running 3.8.13 (unresponsive screen,
only Alt+SysRq+REISUB worked), no relevant error messages in the log.
kernel: [0.00] Linux version 3.8.13-030813-generic (apw@gomeisa) (gcc
version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201305111843 SMP Sat May 11
Public bug reported:
I was prompted to automatically submit this bug report after an
internal system error was detected. All I did was to close the lid
last night and re-open it this morning. Usually the laptop does a
suspend to ram and wakes up again. This time it rebooted and detected a
system
UPDATE:
I re-installed Ubuntu 12.10 from scratch on a new hard drive, no virtualbox
installed yet and I keep getting both false and real GPU lockups. So it seems
like a problem in the 3.5 kernel, which carries through to the 3.8 kernel.
Would the problem likely go away if I changed computers
I have been getting these crash reports over and over again since
yesterday. Every time some other application crashes and generates a
crash report, I get a series of GPU lockup crash reports, to the extend
that I cannot even submit the original crash report because it gets lost
in the flood. Is
I experienced a permanent GPU lock-up today, the screen was unresponsive
for half an hour before I decided to reboot by pressing Alt+SysRq-
REISUB. The below is the the relevant section of kern.log before
shutting down.
** Attachment added: drm:i915_hangcheck_hung and following messages in
Just to add some background information to my previous post:
I have been having random hangups for more than a year now, but only since the
beginning of this week, I have been getting the GPU hang-up error messages.
Today, it coincided with one of the complete lock-ups, that could only be
The workaround in Comment #81 does not get rid of the full problem for
me. I have not been having any false GPU lockup messages any more, but
the computer has crashed twice since, and today I found the GPU-lockup
error message after rebooting. Therefore I submitted a new bug report
here:
Public bug reported:
I have been having random hangups for more than a year now, but only
since the beginning of last week, I have been getting the GPU hang-up
error messages, with or without system hang-ups. This one coincided with
one of the complete lock-ups, that could only be resolved by
Dear Chris,
Thanks for your quick responses. I cannot wait until the release of
raring. Could you tell me a work-around or do you know what version of
Ubuntu/Debian I would need to install to make my system work again?
Thanks for your help!
--
You received this bug notification because you are
I have all updates installed and my system is unusable because of
recurrent gpu lockups. Could someone guide me how to implement the
alleged fixes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, Chris!
Could you also guide me to some instructions how to install these commits?
Sorry, but I haven't dared tinkering with my system at that level yet, but
having no alternatives, I may have to do it. My system is barely usable
right now.
Thanks for your patience!
On Mon, Mar 11, 2013 at
Sorry, I didn't realise that raring is now considered the most up-to-date
release. I meant all updates installed for quantal.
Thanks also for your help regarding my related bug report:
https://bugs.launchpad.net/bugs/1153587
I'll try updating the kernel tonight.
--
You received this bug
I upgraded to Kernel 3.8.2, but it didn't take more than two minutes after
reboot before the GPU lockup crash report reappeared. And it just keeps going...
I suppose it is a different bug, then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks, Chris. Unfortunately, after installing v3.8.2, the GPU-lockup
messages just kept going.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153587
Title:
[sandybridge-m-gt2+ mesa] GPU lockup
GPU -lockup messages started re-appearing, despite an Upgrade to Kernel
3.8.2 in Ubuntu 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001
Same here, tried i915.i915_enable_rc6=0, even upgraded to Kernel
3.8.2, but the crash reports just keep coming, with or without freezes
and hard shutdowns.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to a duplicate bug report (644740).
Just to give an idea of the frequency of the GPU hangs, I pasted below a
part from my syslog. After the 3rd hang in a row, the system became
unresponsive and I had to do an emergency shut-down (Alt+SysRq, R, E, I,
S, U , B). Hope this will help with the troubleshooting.
Mar 11 21:45:03 sppc26
For completeness, below an example from the syslog under Kernel 3.8.2
(again needed emergency reset). I also tried Kernel 2.6.38-13, which did
not result in the same GPU hung message, but lots of other crash
reports, so I gave up quite quickly.
Mar 12 23:01:48 sppc26 kernel: [0.00] Linux
Below is an example from my syslog. I just realised that this is a
slightly different GPU hung message, but the result is the same for
me.
Mar 12 23:01:48 sppc26 kernel: [ 0.00] Linux version 3.8.2-030802-generic
(root@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) )
For completeness, below an example from the syslog under Kernel 3.8.2
(again needed emergency reset). I also tried Kernel 2.6.38-13, which did
not result in the same GPU hung message, but lots of other crash
reports, so I gave up quite quickly.
Mar 12 23:01:48 sppc26 kernel: [0.00] Linux
I wish I could provide that. Just had another fatal GPU hung, but
nothing in i915_error_state:
Mar 13 14:11:56 sppc26 kernel: [ 2601.438055] [drm:i915_hangcheck_hung] *ERROR*
Hangcheck timer elapsed... GPU hung
Mar 13 14:11:56 sppc26 kernel: [ 2601.438060] [drm] capturing error event; look
for
As much as I wish to help debug this, I really need my system to work
again asap. Do you think it would help to do a fresh install of Ubuntu
12.10 or any other linux version? Thanks again for your help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I haven't been able to attach any of the crash reports, because I
get the message that the crash relates to Bug #1059737 and I don't get
an opportunity to upload the report. Bug #1059737 is supposed to be a
duplicate of this bug, which is why I started posting here. How can I
verify whether
Public bug reported:
I am being bombarded with these apports, but whenever I try to identify
an existing bug that resembles this one, the information is not
uploaded and then I'm being told that it may be a different bug.
Therefore I am posting this as a new bug report, hoping that someone
will
Just managed to upload one of the apports as a new bug report here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1154591
Hope the desired information is there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Correct, I had to reboot, as the system became unresponsive. Can I
deactiveate rc6 somehow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153587
Title:
[sandybridge-m-gt2+ mesa] GPU lockup IPEHR:
Thanks, Chris! How can I fix it for my system without installing the
not-yet released raring?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154591
Title:
[sandybridge-m-gt2+] False GPU lockup
Before I do this, could you confirm whether my new report of Bug
#1154591 is related to this here or not? Should I still try removing
i965_dri.so, or has this become irrelevant?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not sure why this does not show up in the bug report, but I am already using
v3.8.2 kernel.
Does this mean that the fix does not work for my system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, to draw things together again:
I originally submitted Bug #1153587, where you identified the missing TLB
invalidate as the reason and suggested that an upgrade to kernel v3.8 would fix
it. I installed Kernel v3.8.2 but the problems continued. You asked to provide
Thanks for putting my issues in context with the rest.
However, I'm still confused, as the 4th line of the above bug report says:
Uname: Linux 3.8.2-030802-generic x86_64
I currently have the i915.i915_enable_rc6=0 set (see e.g.
Thanks heaps! I modified the line in grub accordingly and I am about to
reboot. Will let you know if it makes much of a difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154591
Title:
Unfortunately, an hour later, apport catapulted me back onto this site. So this
is with the 3.8.2 kernel and with the line GRUB_CMDLINE_LINUX_DEFAULT=quiet
splash i915.semaphores=0 i195.i915_enable_rc6=0
in grub.
This time, I cannot find any error messages relating to i915 in the syslog or
I am affected by the same bug and followed this post to change the
xorg.conf settings: http://ubuntuforums.org/showthread.php?t=1883119
So the text used is:
SubSection Display
Depth 24
Virtual 2304 2048
EndSubSection
This did not help.
Thanks for the tip about Acroread. I also found another workaround.
Printing to file using cups-pdf creates a file that shows smooth
gradients in Evince.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The computer was acting strange, so I clicked on Shut down. An error
message about Nautilus came up, I asked to force quit, then the shutdown
proceeded very slowly until it hang on a black screen. No response to
any shortcuts, so I had to do a hard reset. Got the crash report
Thanks, peterbo, for the link incl. installation instructions!
Unfortunately after two days, I had another crash with the new kernel on Ubuntu
12.10. The mouse and keyboard stopped responding and before I could try to do
CTRL+ALT+F4 or CTRL+ALT+SysRq+REISUB, the laptop just turned itself off.
Thanks, peterbo. Sorry, got confused. Of course, I'm running it on
13.04, too. I have had these really weird crashes before (rebooting by
itself) and they went away after one of the kernel upgrades, maybe even
when upgrading from 12.10 to 13.04. Got the Hangcheck timer elapsed ones
instead.
Just confirming that the kernel under http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11-rc5-saucy/ is not usable to me. My laptop crashes
unrecoverably within hours and does not leave any traces in syslog.
About to remove it again from the kernel list.
3.11.0-031100rc5-generic from
Oops, wrong copy and paste, sorry!
3.11.0-031100rc5-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc5-saucy/ crashes several
times a day
3.11.0-994-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/
crashes every couple of days on my
After half a day of working on 3.8.13-030813-generic, got the
[drm:i915_hangcheck_hung] again. At least it was sort-of recoverable,
as I was able to log into another tty and backup i915_error_state
(attached). Hope it helps someone for diagnosing the problem. When
returning to tty7, Screen was
Dear Chris, thanks for the tip. I upgraded my bios last night and will
see if the problem re-occurs. However, I have been having lots of other
problems and started using a newer kernel to keep my machine in working
condition, while I haven't been pointed to this bug report again. So I
won't be
UPDATE:
My two displays work now without error messages. I followed the following
tutorial to install the newest driver from the ATI web site:
http://wiki.cchtml.com/index.php/Ubuntu_Oneiric_Installation_Guide
Then I had the following error message when running fglrxinfo: Error of
failed
Public bug reported:
I switched from Legacy to EFI boot using a live CD and boot-repair. The
system booted fine, but when running a software update, an error message
appeared, asking me to report a bug, so here it is.
Ubuntu Gnome 15.10
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package:
I have the same problem, trying to install docker inside a docker image of
Ubuntu 16.04 and following instructions at:
https://docs.docker.com/engine/installation/linux/ubuntu
If there is another way to achieve this task or fundamental reasons for not
even trying, please let me know.
--
You
61 matches
Mail list logo
