Problem is intermittent for me.
When I posted my previous comment, I had just done a fresh boot from
power-off (I never use hibernate or suspend, and don't even have any
swap partition or swap file configured), and had gotten the error on
that boot, and guvcvideo didn't work.
I just did 4 more
I get this too on a 5th gen Lenovo X1 Carbon and mainline kernel.
4.20.0-042000rc7-generic at he moment, but it's been happening for some
time not just this exact kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am seeing the same scrollbars in other apps but not all other apps.
I get the same small scrollbars in Firefox, Thunderbird, LibreOffice, and
Evince, as a few examples. There are others.
Meanwhile at the same time, other apps respect the desktop theme and get
a different scrollbar. Gimp,
The same too-small scrollbars are in Mozilla Thunderbird too.
I don't know how/why this is not considered a bug or at least a regression.
Thunderbird and Firefox used to be usable, and now they are both more difficult
to use. Other apps on the same system/desktop don't have the problem.
--
You
Yes! You are right it's Thunderbird too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683997
Title:
Firefox scrollbars are too narrow and difficult to use in Zesty
To manage notifications about
Same here. I had to write myself a google drive doc that I could consult
every time a the grub-efi package was updated and broke my boot again.
In addition to the steps explained previously, I also copy my working
manually edited grub.cfg to emergency.cfg, so that every time I get a
failed boot
I have this on numerous 4.13 and 4.14 kernels from synaptic (17.10 repos) and
ubuntu-mainline ppa.
IE today:
4.14.17-041417-generic #201802031230 SMP Sat Feb 3 17:31:50 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
This is on a 5th get lenovo x1 carbon using the built-in bluetooth and a
few
Me too. It's extremely difficult to get into the scrollbar using my
laptops touch pad. Even though I go slow and creep forward, it always
either stops before or shoots beyond. A good mouse might not be so bad,
but it's impossible with most touch pads, *especially* on high dpi
display. Both of
This goes back to at least 2014.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772571
Except it sounds like maybe it shouldn't be using hciconfig at all for bt for
other reasons:
http://www.spinics.net/lists/linux-bluetooth/msg64021.html
So, bluetoothctl? btmgmt?
Maybe it's just as well
** Tags added: raring saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/567226
Title:
Black Border around Splash Image
To manage notifications about this bug go to:
Well lubuntu raring uses lightdm not lxdm, so assuming saucy does too,
at least that doesn't conflict with the idea that maybe lxdm was doing
or failing to do something. That's really all I changed was installing
slim, selecting it as default display manager, uninstall lxdm, reboot.
--
You
Same here, 98/99% cpu.
Only with --desktop.
Running pcmanfm with no arguments to get the ui is ok.
I tried removing ~/.config/pcmanfm to let it re-create from scratch but
it didn't help.
strace attached (3 seconds then ctrl-c)
** Attachment added: strace -o pcmanfm-desktop-strace.txt pcmanfm
Forgot to say this is pcmanfm 1.1.0-0ubuntu2 from Raring.
Precise and Quantal were ok.
bkw@noexcuse:~$ apt-cache policy pcmanfm
pcmanfm:
Installed: 1.1.0-0ubuntu2
Candidate: 1.1.0-0ubuntu2
Version table:
*** 1.1.0-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ raring/universe
Correction. I just downgraded pcmanfm to 1.0.1-0ubuntu1 from Quantal (rest of
machine is still Raring) and it still behaves the same.
Trying Precise next.
Note this install is Raring but updated from Bodhi Linux 2.0 to Precise
to Quantal to Raring. There are still Bodhi packages and configs
Confirmed, downgrading to 0.9.10-0ubuntu2 from Precise works ok.
No other changes (to configs, etc) other than the fact that forcing that
version of pcmanfm pulled in some other older versions of other packages.
root@noexcuse:~# apt-cache policy pcmanfm
pcmanfm:
Installed: 1.0.1-0ubuntu1
Bear with me through what seems OT...
Well I don't know how this can help, but, the same dist-upgrade from
Quantal to Raring also broke lxdm or lxsession for me. lxdm would show
the greeter and accept the login info, but then would not launch
lxsession, or, maybe it started lxsession but
Public bug reported:
man mount says:
[CODE]
mount [-l] [-t type]
lists all mounted filesystems (of type type).
The option -l adds the labels in this listing.
[/CODE]
Yet mount and mount -l do not show my root filesystem /
Which of course is mounted.
df, df -h, df -ah don't show it either.
Same here, gma500, kernels 3.2.0, 3.5.0, and 3.6.0 though I think it's
more a xorg problem than kernel.
For me these two things work:
echo 75 /sys/class/backlight/psb-bl/brightness
and
xrandr --output LVDS-0 --set backlight 75
But xbacklight does not, and enlightenment 17's backlight module
Public bug reported:
gma500, kernels 3.2.0, 3.5.0, and 3.6.0
Currently:
bkw@noexcuse:~$ uname -a
Linux noexcuse 3.6.0-030600-generic #201209302035 SMP Mon Oct 1 00:43:10 UTC
2012 i686 i686 i686 GNU/Linux
bkw@noexcuse:~$ lsmod |grep gma
gma500_gfx198198 2
drm_kms_helper
/sys/class/backlight/psb-bl/brightness works fine.
The xrandr program also works fine.
This script, which uses either of those, works fine.
http://code.google.com/p/bltool/
Only xbacklight doesn't, and at least some other things, such as the
backlight module in enlightenment 17.
--
You
Previously the best work-around I found was creating a file
/boot/grub/custom.cfg with this in it:
[CODE]
# Manually re-load gfxterm
# update-grub generates a grub.cfg that thinks grub can see the SD card reader
# (where / lives) at boot time to get the font for gfxterm from /usr/share/...
# So
Public bug reported:
Sony Vaio P
Ubuntu Precise and Quantal
kernel 3.5.0
gma500_gfx kernel driver
modesetting xorg driver
Assume the current quantal quantal-proposed versions of everything.
xbacklight doesn't work. No backlight change, and no output from the program.
xbacklight and xbacklight
This admittedly minor annoyance still exists in quantal.
The fix is trivial.
Can we please get line 37 in grub2-1.99/grub-core/term/gfxterm.c
changed from
#define DEFAULT_BORDER_WIDTH 10
to
#define DEFAULT_BORDER_WIDTH 0
That's it.
Please?
It's been a long time already.
--
You received
** Tags added: maverick natty oneiric quantal
** Tags removed: amd64 apport-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/567226
Title:
Black Border around Splash Image
To manage
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/567226
Title:
Black Border around Splash Image
To manage notifications about this bug go to:
Ubuntu 12.04 with grub 1.99-21ubuntu3.1
Same problem here but not because of btrfs or any other filesystem
support.
In my case it's because / lives on a built-in sdcard reader in a Sony Vaio P
netbook.
The card reader is not bootable, has no bios support, and at boot time grub has
no driver
[quote]The backlight works WITHOUT the poulsbo driver.
well works with a script to manage brightness as my function keys do
not always work, even with the kernel options acpi_backlight=vendor and
acpi_osi=Linux.[/quote]
How does this work exactly?
I have precise beta and kernel
It works.
wget ftp://ftp.gnu.org/gnu/grub/grub-1.99.tar.gz
tar xvzf grub-1.99.tar.gz
cd grub-1.99
vi grub-core/term/gfxterm.c
change this line:
#define DEFAULT_BORDER_WIDTH 10
to this:
#define DEFAULT_BORDER_WIDTH 0
./configure
make
sudo mv /boot/grub/gfxterm.mod
gfxterm.mod from grub 1.99 compiled on Precise i386 per above
directions.
I would rename the old gfxterm.mod to gfxterm_old.mod so that if it doesn't
work on your machine for some reason, you can manually say
rmmod gfxterm
insmod gfxterm_old
in the grub recovery shell. You can also always
Correction (not harmful) to the build/install directions. After compile
the new gfxterm.mod is found in the grub-core directory not in the
grub-1.99 top level directory. So the cp command to install is:
sudo cp grub-core/gfxterm.mod /boot/grub/gfxterm.mod
--
You received this bug notification
Looks like it might be caused by DEFAULT_BORDER_WIDTH in grub-
core/term/gfxterm.c
http://bzr.savannah.gnu.org/lh/grub/branches/release_1_99/annotate/head
:/grub-core/term/gfxterm.c
But I still don't see any way to change it other than editing that #define and
recompiling.
Trying that now...
Happens to me too.
Oneiric, Sony Vaio P, 1600x768 image.
I can tell from the details of the image that it is NOT being scaled, it
is being cropped.
It would be impossible to detect such a small amount of scaling by eye
with that many pixels on that small of a screen, but there are detailed
Same problem.
OS: oneiric, 3.0.0-17
System: Sony VGN-P530H
bluetooth:
Internal, usb-connected,
Bus 003 Device 002: ID 044e:3017 Alps Electric Co., Ltd BCM2046 Bluetooth
Device
Receiver: Sony HWS-BTA2W
90% idle cpu, idle disk, pandora streaming in over wifi, using pianobar
commandline
Agreed.
The logic behind making the new default is based on assumptions which
are surely wrong.
The logic behind making this default, whether it's terrible or sensible,
take place in the kernel instead of in X or the desktop environment is
inexplicable.
The logic behind requiring the user to
Sounds like the issue is known and acknowledged enough that further
proof of it's existence isn't needed but just for the record the same
thing happens to me.
Desktop machine in my case which I don't believe was originally using nm. It
definitely always had a static ip, (I occasionally use it to
I updated the Fn / F-keys directions here for Jaunty:
https://help.ubuntu.com/community/AppleKeyboard
It's essentially the same directions but the names of things changed in
Jaunty.
change:
modprobe.d/* files should be *.conf now as later anything not *.conf will be
ignored, though for now it
Windows does many things in brute force inelegant ways in order to attain that
superiority.
I would rather my software be efficient and I would rather know when my
hardware (or network, or any number of configurations) has a problem and get it
fixed. It's a somewhat religeous or philosophical
Well I've been poking at this a bit and have learned a few things.
I don't think the code in the fix_usb_hd.sh above is quite right. using expr to
get character 3 out of argv1 which was supplied via the udev rule code %k and
then using that value as part of the path to a spot under /sys for
I think I found another possible fix, Totally simple and userspace too.
I have a Seagate FreeAgent 500gb and I beleive I am having the drive
turns off problem and not the can't handle much traffic problem. BTW
it seems to be common to all linux not just ubuntu. I have this problem
on suse 10.2.
Awsome thanks for the more specific udev rule. That's ideal since it
would apply to any FreeAgentDesktop, which obviously they all have the
same problem.
Also, by now I think I can say the sdparm fix works.
Without rebooting I did the disconnect/reconnect I mentioned, then
manually did the
40 matches
Mail list logo
