Still a problem on Mint 18.3 64-bit
Kernel 4.13.0-32
Cinnamon 3.6.7
This bug has been being reported on now for 3 years without anyone
assigned to it. What do we need to do to move it forward?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This seems to still be an issue. For instance, when I launch the System
Settings dialog on my laptop (1360x768), the window extends below the
bottom of my screen such that I can't see the Users icon. This
window, as far as I can tell, is not resizable or maximizable, and no
scroll bar is
Public bug reported:
In 13.04, when I open the system settings dialog for mouse pointer speed
and adjust it to my liking, it reverts to default settings as soon as I
close the dialog window. If I leave the window open, all works as it
should. What info would be useful in tracking this down?
@Andre: well I'll be damned... Yes, you're right, it's 12.04.2 -- I
hadn't noticed the change from 12.04.1. It's working fine now, but I'm
confused as to how any of the updates I just installed could have any
impact -- just openjdk and some other minor items. Strange. I'll let
you know if it
Still a problem. I'm on 12.04.1 with all updates. Same behavior as
Eduards describes in post 23. Sandy Bridge graphics, Compiz enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886605
Title:
Update: I installed the 3.2.0 Kernel and now the proprietary graphics
work. Apparently the bug in the Sandybridge Kernel modules has been
fixed as of 3.2. I can boot without the nomodeset, etc., and the
graphics show as Intel Sandybridge Desktop. Unfortunately, I still
can't run Compiz, so I'm
I'm having the same problem now. Oneiric. Lots of disk space,
permissions look fine. Tomboy log attached. Suggestions?
Thanks!
Alan
** Attachment added: tomboy.log
https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/513945/+attachment/2638694/+files/tomboy.log
--
You received this
Workaround: all kernels will boot and run fine if I add nosplash
nomodeset to GRUB_CMDLINE_LINUX_DEFAULT. I have successfully
upgraded to Oneiric, but can only run with the VESA driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bump.
Does anyone have any ideas here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887756
Title:
Black screen on boot with sandy bridge processor
To manage notifications about this bug go to:
Public bug reported:
This is on an HP Compaq 8200 Elite all-in-one, with an Intel i3-2100.
The live CD for Oneiric boots to a black screen. I instead installed
Lucid, which works fine, but without proprietary graphics abilities.
Upgrade to Natty resulted in a black screen on boot again. Booting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887756
Title:
Black screen on boot with sandy bridge processor
To manage notifications about this bug go to:
I can confirm this bug as well. Same behavior. I'll provide my
hardware info when I go home tonight, but I'm running Lucid with all
current updates.
--
[fglrx] GL screensaver obscures window to enter password when lock is enabled
https://bugs.launchpad.net/bugs/569993
You received this bug
@Tormod -- your setup seems to be quite different for those two
bootcharts. The one for s- is loading a lot fewer services (no compiz,
no panel, etc.). I think if you try s- vs. u- with otherwise identical
setups you'll find u- to be much faster than s-. (Also, your boots are
pretty nice and
** Attachment added: sreadahead, ureadahead
http://launchpadlibrarian.net/35561981/bootcharts.zip
--
performs poorly on slow HDD
https://bugs.launchpad.net/bugs/432089
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I actually switched to ureadahead several days ago -- can't remember how
the idea came up -- so I don't have charts for right before and right
after, but here's the best I've got.
Ureadahead a great improvement -- by stopwatch from 2:30 with s- down to
1:30 with u-
I too have much disk
Oh, one more thing. There's a point early in the boot when it says
Starting AppArmor Profiles. It gets stuck on this for more than 30
seconds before it continues displaying boot messages. Is it actually
doing anything during this time?
--
performs poorly on slow HDD
When I try to upload my bootcharts I get the message cannot upload
empty file. Suggestions? They all open fine for me to examine.
--
performs poorly on slow HDD
https://bugs.launchpad.net/bugs/432089
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, I too have this problem. Jaunty took about 1 minute, Karmic more
than 2 (although bootchart shows it as 1:35 the desktop is not loaded to
the point of useability by then). And yes, I found early alphas to boot
much better than the versions after the switchover to upstart. It
switches
** Summary changed:
- USB Mass Storage Phone gives Error -5 On Probe
+ SOLVED - USB Mass Storage Phone gives Error -5 On Probe
--
SOLVED - USB Mass Storage Phone gives Error -5 On Probe
https://bugs.launchpad.net/bugs/407746
You received this bug notification because you are a member of Ubuntu
Workaround for this issue: add usb-storage option_zero_cd=2 to /etc/modules.
After that it worked fine for me until I upgraded to Karmic. Then no error,
but no mount either. I'm told the drawback to this workaround is that modems
with an emulated windows driver cd probably won't work.
-AG
Well, it seems you're right. HP is extending the warranty and replacing
faulty wireless components in quite a few laptop models. (Not mine,
though,.. at least not yet.) Here's the link --
http://h10025.www1.hp.com/ewfrf/wc/document?lc=endlc=encc=cadocname=c01087277#c01087277_identify
It seems
That workaround doesn't work for me. Still no detection of my wireless
(4311) hardware. Now running Karmic Alpha 6, so it's not fixed in the
newest Kernel. I do think this is a kernel bug -- it's the kernel that
should be detecting the hardware correctly and passing it along to the
rest of the
I'm having the identical problem with a Compaq Presario F700. My
Broadcom wireless is not detected. Does not appear in lspci. This in
Jaunty with all updates including proposed. At one point it was
detected, and selecting the b43 driver worked well. After waking from
sleep it was gone -- no
Still the same problem with 2.6.28-15 Kernel.
Anyone have any ideas on this one?
-Alan
--
USB Mass Storage Phone gives Error -5 On Probe
https://bugs.launchpad.net/bugs/407746
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
And fails to mount. This error began with Jaunty. My phone works fine
if I boot with the live CD into Intrepid 8.10. In 9.04 the phone begins
to connect, then encounters an error and never gets fully connected.
Attached is the dmesg and lsusb for both the failed 9.04 and
** Attachment added: dmesg_lsusb9.04_8.10
http://launchpadlibrarian.net/29777699/dmesg_lsusb9.04_8.10
--
USB Mass Storage Phone gives Error -5 On Probe
https://bugs.launchpad.net/bugs/407746
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Stefan, not sure if you need to know, but I did finally get around to
collecting the info and submitting a new bug report. It's Bug #407746.
Thanks again,
Alan
--
[intrepid] USB mass-storage doesn't mount automatically with nokia 5610 express
with 2.6.27-7 latest
More info: I did try booting with usbcore.old_scheme_first=1. I'm not sure
I did it right, as there was no modprobe.conf file, so I created one. That
didn't work. I also tried entering modprobe usbcore old_scheme_first=1 at
the terminal and got back FATAL: Module usbcore not found.
I too have this problem. Jaunty 9.04 with current updates. LG Shine
CU-720.
If I boot Intrepid from the live CD my phone connects with no problem.
Thanks!
** Attachment added: Here's the relevant output from dmesg and sudo lsusb
-vvv:
http://launchpadlibrarian.net/28645731/USB%20Fail
--
29 matches
Mail list logo
