[Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
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 power-off reboots (using "shutdown" from the LXDE shutdown menu, not "reboot" or "suspend" etc) , and I didn't get the error any of those times, and guvcvideo worked in each of those sessions. Same kernel each time, (4.20.0-042000rc7-generic). Two of the boots I pressed enter in grub to skip the grub timeout, 2 times I let grub time out, no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
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. https://bugs.launchpad.net/bugs/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675496] Re: Scrollbars are tiny in Firefox (since FF 52)
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, Leafpad, and gFTP are examples. These are the purple ones in the attached pic. ** Attachment added: "image of scrollbars from different apps on the same desktop at the same time" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1675496/+attachment/5121285/+files/scrollbars.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675496 Title: Scrollbars are tiny in Firefox (since FF 52) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1675496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767040] Re: Firefox doesn't use overlay scrollbars
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767040 Title: Firefox doesn't use overlay scrollbars To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/767040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683997] Re: Firefox scrollbars are too narrow and difficult to use in Zesty
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652822] Re: grub efi doesn't install fs module needed to access root
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 again after a system update, I pull up google drive on my
phone to read this emergecy manual boot command:
grub> configfile ${cmdpath}/emergency.cfg
That one command is all you need to enter manually when you are faced
with the grub> prompt at boot, and it loads the rest of your normal grub
config, and you boot normally.
Then once booted, copy emergency.cfg back over grub.cfg, and update the
copy of xfs.mod since it might have been updated by the very update that
regnerated grub.cfg.
https://drive.google.com/open?id=1B2FrtIaG75PhFPsjzXnJS0MeDg7rezEP3Ef5fFlrLAo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1652822/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react
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 different bt mice, IE HP and Verbatim. The rfkill block/unblock commands above did nothing for me. cpu is eating my battery and the only process is "kworker" 2615 root 20 0 0 0 0 R 85.3 0.0 6:02.78 kworker/0:2 3365 root 20 0 45376 3928 3260 R 0.3 0.0 0:00.04 top 1 root 20 0 220176 8432 6316 S 0.0 0.1 0:02.59 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H 6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq powertop says... The battery reports a discharge rate of 18.6 W The estimated remaining time is 2 hours, 26 minutes Summary: 655.9 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 5.6% CPU use Usage Events/sCategory Description 80.0% Device Display backlight 6.1 ms/s 256.3Interrupt [9] acpi 23.8 ms/s 233.4kWork acpi_os_execute_deferred 2.7 ms/s 67.4Process/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolis 1.0 ms/s 25.4Processlxterminal 445.6 µs/s 13.9Interrupt PS/2 Touchpad / Keyboard / Mouse 42.0 µs/s 13.5Process[xfsaild/nvme0n1] 442.2 µs/s 12.2Processlxpanel --profile Lubuntu ... I have to reboot to clear it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683997] Re: Firefox scrollbars are too narrow and difficult to use in Zesty
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 which features apply to my brand new Lenovo X1 Carbon. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717090] Re: powertop tries to execute hardcoded /usr/sbin/hciconfig
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 this hard-coded path is wrong, because after I create a symlink to /bin/hciconfig, powertop hangs sometimes on startup, and any time Itry to toggle bluetooth from within powertop. At least with the broken hardcoded path, everything else works! ** Bug watch added: Debian Bug tracker #772571 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772571 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717090 Title: powertop tries to execute hardcoded /usr/sbin/hciconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/1717090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
** 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913273] Re: PCManFM consumes 90% CPU
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913273 Title: PCManFM consumes 90% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913273] Re: PCManFM consumes 90% CPU
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 --desktop https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+attachment/3685122/+files/pcmanfm-desktop-strace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913273 Title: PCManFM consumes 90% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913273] Re: PCManFM consumes 90% CPU
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 i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913273 Title: PCManFM consumes 90% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913273] Re: PCManFM consumes 90% CPU
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 lingering. pcmanfm has been ok until I updated sources.list to Raring though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913273 Title: PCManFM consumes 90% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913273] Re: PCManFM consumes 90% CPU
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 Candidate: 1.1.0-0ubuntu2 Version table: 1.1.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages 1.1.0-0ubuntu1~precise.1 0 -10 http://packages.bodhilinux.com/bodhi/ precise/testing i386 Packages *** 1.0.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages 100 /var/lib/dpkg/status 0.9.10-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ precise/universe i386 Packages root@noexcuse:~# apt-get install pcmanfm=0.9.10-0ubuntu2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfm-gtk-bin libfm-gtk3 libfm3 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libfm-gtk1 libfm1 libmenu-cache1 The following NEW packages will be installed: libfm-gtk1 libfm1 libmenu-cache1 The following packages will be DOWNGRADED: pcmanfm 0 upgraded, 3 newly installed, 1 downgraded, 0 to remove and 1 not upgraded. Need to get 51.5 kB/455 kB of archives. After this operation, 447 kB of additional disk space will be used. Do you want to continue [Y/n]? And now pcmanfm --desktop uses 0.7% cpu instead of 99% root@noexcuse:~# ps auxw |grep pcmanfm bkw 2580 0.7 0.5 84044 10428 pts/3S+ 14:52 0:00 pcmanfm --desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913273 Title: PCManFM consumes 90% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913273] Re: PCManFM consumes 90% CPU
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 lxsession immediately crashed. In any event, neither lxsession nor any of the things it's autostart file listed were in the process list. But manually running export DISPLAY=:0 ; lxsession from a console screen worked. I couldn't figure out why lxdm wasn't launching lxsession as it used to before the upgrade, so I uninstalled lxdm and install slim. slim worked normally, launching my same old lxsession. And somehow, pcmanfm from raring works too now. No more 100% cpu usage from pcmanfm --desktop even though I've upgraded back to the current pcmanfm from raring. So perhaps the problem is as much lxdm failing to provide something for pcmanfm as it is pcmanfm failing rather ungracefully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913273 Title: PCManFM consumes 90% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065303] [NEW] mount does not display all mounted filesystems, including /
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. /proc/mounts does show it. df will show it only if explicitly specified. mount / will also correctly state that it is already mounted. [CODE] root@noexcuse:~# cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=1017316k,nr_inodes=215199,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=410772k,mode=755 0 0 /dev/disk/by-uuid/f2a55331-1549-4c25-8aa9-204275068771 / btrfs rw,noatime,nospace_cache 0 0 none /sys/fs/fuse/connections fusectl rw,relatime 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0 /dev/sdc1 /winloader fuseblk rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0 /dev/sdc2 /windows fuseblk rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 gvfsd-fuse /home/bkw/.gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 root@noexcuse:~# root@noexcuse:~# mount -l proc on /proc type proc (rw) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) /dev/sdc1 on /winloader type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096) [System Reserved] /dev/sdc2 on /windows type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfsd-fuse on /home/bkw/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=bkw) root@noexcuse:~# root@noexcuse:~# ls -lL /dev/disk/by-uuid/f2a55331-1549-4c25-8aa9-204275068771 brw-rw 1 root disk 8, 0 Oct 10 16:38 /dev/disk/by-uuid/f2a55331-1549-4c25-8aa9-204275068771 root@noexcuse:~# ls -l /dev/disk/by-uuid/f2a55331-1549-4c25-8aa9-204275068771 lrwxrwxrwx 1 root root 9 Oct 10 16:38 /dev/disk/by-uuid/f2a55331-1549-4c25-8aa9-204275068771 - ../../sda root@noexcuse:~# root@noexcuse:~# df -ah Filesystem Size Used Avail Use% Mounted on proc 0 0 0- /proc sysfs 0 0 0- /sys udev994M 4.0K 994M 1% /dev devpts 0 0 0- /dev/pts tmpfs 402M 1008K 401M 1% /run /dev/sdc1 350M 203M 148M 58% /winloader /dev/sdc256G 24G 33G 42% /windows binfmt_misc0 0 0- /proc/sys/fs/binfmt_misc gvfsd-fuse 0.0K 0.0K 0.0K- /home/bkw/.gvfs root@noexcuse:~# root@noexcuse:~# df -h / Filesystem Size Used Avail Use% Mounted on -31G 16G 14G 55% / root@noexcuse:~# # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/sdc1 Windows 8 loader UUID=E8C6C56EC6C53D96 /winloader auto noatime 0 0 # /dev/sdc2 Windows 8 C: UUID=12E2D580E2D5688D /windows auto noatime 0 0 # memorystick btrfs 32g UUID=f2a55331-1549-4c25-8aa9-204275068771 / auto noatime 0 0 [/CODE] / is a btrfs filesystem on a memorystick card in a laptop card reader slot, the entire raw card device, IE /dev/sda not a partition, shown by the /proc/mounts and ls -l output above. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: mount 2.20.1-5.1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Wed Oct 10 18:28:51 2012 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065303 Title: mount does not display all mounted filesystems, including / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1065303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338733] Re: Unable to adjust of brightness on Tabletkiosk Sahara TouchIT-213 Tablet PC
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 does not. note: For me, there is also a /sys/class/backlight/acpi_video0/brightness which only takes values from 0-to8 and which does not actually work. Also, for me, setting acpi_backlight=vendor on the grub command line results in there not being a /sys/class/backlight/psb-bl/ directory any more, instead in it's place there is /sys/class/backlight/sony or maybe it was sonypi , but it works the same. It didn't make xbacklight start working nor e17's backlight module, and xrandr and sysfs (under the new name) both still worked. As a work-around I wrote and am using this in the meantime: http://code.google.com/p/bltool/ In my desktop I configured the keybindings for the hardware Fn keys for backlight (XF86MonBrightnessDown XF86MonBrightnessUp) to execute the commands bltool - and bltool +. Plus a menu shortcut to just run bltool with no options for a manual interactive slider. You can also put it in a startup script or a laptop battery mode vs wall power script and set arbitrary leveles like bltool 45 and bltool 100 All values are 0 to 100 percent. The script translates to whatever the range is used by your particular driver, be it 0-8, 0-32, 0-100, 0-127, 0-255 etc. So if your driver uses 0-255, you still say 50 if you want 50%, and it will figure out for itself to use 127 internally. It even works outside of X. If you are at a text console it will uses sysfs instead of xrandr. If you haven't written a .bltool config file it will scan the sysfs directory and prompt you to pick one of the backlight directories it finds there. At the console it will use dialog, in X it will use zenity. The only thing it won't do automatically is create the udev rul that allows regular users to write to the sysfs files, but bltool --help includes a rule you can just cut paste and explicit instructions what file name to create and paste into. And that's only needed for sysfs. the default mode is to use xrandr which is slower but doesn't need a udev rule to work. There is also a pre-made udev rule file in the download section of the bltool page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/338733 Title: Unable to adjust of brightness on Tabletkiosk Sahara TouchIT-213 Tablet PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xbacklight/+bug/338733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1060431] [NEW] xbacklight doesn't do anything, not even error message.
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 45427 1 gma500_gfx drm 227730 3 gma500_gfx,drm_kms_helper i2c_algo_bit 13316 1 gma500_gfx video 18908 1 gma500_gfx bkw@noexcuse:~$ dpkg-query -W xserver-xorg xserver-xorg1:7.7+1ubuntu3 xbacklight and enlightenment 17 backlight module don't do anything. xbacklight doesn't even output an error message or anything no matter what command line options are used. However, both of these two things DO work: echo 75 /sys/class/backlight/psb-bl/brightness and xrandr --output LVDS-0 --set backlight 75 For me, there is also a /sys/class/backlight/acpi_video0/brightness which only takes values from 0-8 and which does not work. Also, for me, setting acpi_backlight=vendor on the grub command line results in there not being a /sys/class/backlight/psb-bl/ directory any more, instead in it's place there is /sys/class/backlight/sony or maybe it was sonypi , but it works the same as psb-bl. It didn't make xbacklight start working nor e17's backlight module. xrandr and sysfs (under the new name) both still worked the same. As a work-around I wrote and am using this in the meantime: http://code.google.com/p/bltool/ ** Affects: xbacklight (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 + gma500_gfx198198 2 drm_kms_helper 45427 1 gma500_gfx drm 227730 3 gma500_gfx,drm_kms_helper i2c_algo_bit 13316 1 gma500_gfx video 18908 1 gma500_gfx bkw@noexcuse:~$ dpkg-query -W xserver-xorg xserver-xorg 1:7.7+1ubuntu3 - bkw@noexcuse:~$ xbacklight and enlightenment 17 backlight module don't do anything. xbacklight doesn't even output an error message or anything no matter what command line options are used. However, both of these two things DO work: echo 75 /sys/class/backlight/psb-bl/brightness and xrandr --output LVDS-0 --set backlight 75 For me, there is also a /sys/class/backlight/acpi_video0/brightness which only takes values from 0-8 and which does not work. Also, for me, setting acpi_backlight=vendor on the grub command line results in there not being a /sys/class/backlight/psb-bl/ directory any more, instead in it's place there is /sys/class/backlight/sony or maybe it was sonypi , but it works the same as psb-bl. It didn't make xbacklight start working nor e17's backlight module. xrandr and sysfs (under the new name) both still worked the same. As a work-around I wrote and am using this in the meantime: http://code.google.com/p/bltool/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060431 Title: xbacklight doesn't do anything, not even error message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xbacklight/+bug/1060431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054298] Re: xbacklight doesn't work, but xrandr does and so does /sys/class/backlight
/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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054298 Title: xbacklight doesn't work, but xrandr does and so does /sys/class/backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615769] Re: fonts should be installed to /boot/grub
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 we do manually here what update-grub fails to do automatically in grub.cfg insmod part_msdos insmod ntfs set root='(hd0,msdos2)' search --no-floppy --fs-uuid --set=root 12E2D580E2D5688D if loadfont /linux_boot/grub/fonts/unicode.pf2 ; then set locale_dir=($root)/linux_boot/grub/locale set lang=en_US set gfxmode=1600x768x16 set gfxterm_font=unicode load_video insmod gfxterm insmod gettext insmod png terminal_output gfxterm background_image /linux_boot/grub/VaioP_Green.png fi [/CODE] That's arcane and full of ugly hard-coded stuff that will break and update-grub will not update when the underlying details change. That root= and uuid point to the windows ntfs partition C: drive on the main pata drive. The path /linux_boot is a directory C:\linux_boot on that ntfs filesystem. (/boot is symlinked to /windows/linux_boot. Remember / is not visible to grub at boot time.) This works, but I finally found instead of all that junk you don't need any custom.cfg at all unless you need it for other stuff. Recent versions of grub2 copy unicode.pf2 to /boot/grub/fonts. As long as that's there, then all you need to do is one time run this: grub-editenv - set feature_default_font_path=y Now update-grub still produces a grub.cfg that points to /usr/share , but now this part gets invoked instead of the part that tries to use the unreachable path: if [ x$feature_default_font_path = xy ] ; then font=unicode else You only have to run it once and subsequent update-grub doesn't break it. As far as I'm concerned this is almost as good as a variable in /etc/default/grub. It's main problem is it's unfindable in any documentation. But it satisfies my request above for a way to tell it not to try to use / . There does seem to be an undocumented variable GRUB_FONT that you can put in /etc/default/grub, but I couldn't figure out how to make it work. No matter what I put in there, it would just break update-grub. root@noexcuse:~# update-grub Generating grub.cfg ... /usr/sbin/grub-probe: error: failed to get canonical path of unicode.pf2. /usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map. root@noexcuse:~# unicode unicode.pf2 fonts/unicode.pf2 grub/fonts/unicode.pf2 /linux_boot/grub/fonts/unicode.pf2 /boot/grub/fonts/unicode.pf2 all failed the same way And pinfo grub does not say anything about it. It didn't say anything about feature_default_font_path either, I found that by reading the scripts and the generated grub.cfg and GUESSING. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615769 Title: fonts should be installed to /boot/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/615769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054298] [NEW] xbacklight doesn't work, but xrandr does and so does /sys/class/backlight
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 -get show nothing, no output from the program at all. xbacklight -set50 and xbacklight-d :0 -set 50 does nothing nor prints any output. However both sysfs and xrandr work fine. Specifically: xrandr --verbose lists outputs and shows the main screen has backlight property, and xrandr --output LVDS-0 --set backlight 50 changes the backlight brightness. And cat /sys/class/backlight/psb-bl/actual_brightness shows the current brightness, and echo 50 /sys/class/backlight/psb-bl/brightness changes the brightness. I have written the following script to use in place of xbacklight: http://forums.bodhilinux.com/index.php?/topic/5985-brightness-scripts/page__view__findpost__p__56911 This script, both the sysfs and xrandr methods of it, works fine for me on the same machine. (for sysfs, I had to make a udev rule to allow users to write to the sysfs files, as noted on that page and in the --help output of the script) It requires zenity for the user interactive options. Not needed for the non-interactive options. -- bkw ** Affects: 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/1054298 Title: xbacklight doesn't work, but xrandr does and so does /sys/class/backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1054298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
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 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
** 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615769] Re: fonts should be installed to /boot/grub
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 that can see it. /boot does live on a bootable drive, a usb stick, and internal hd is all Windows 8 Consumer Preview. So /boot is on a small removable usb drive and / is entirely on a 32G sdcard. update-grub generates a grub.conf that refers to (sdcard,partition)/usr/share/... for background image and for font. At boot time, sdcard is not is not accessible and so the loadfont line fails, and so gfxterm does not load. Booting still works. It fails gracefully and falls back to a non-gfxterm plain text mode that functions. The wallpaper image can be taken care of by copying it to somewhere under /boot and editing /etc/default/grub to reflect that. But the font is still a problem. If I manually copy unicode.pf2 to /boot/grub, and manually change /boot/grub/grub.cfg to refer to the external usb drive that /boot lives on instead of the internal card reader that / lives on, then at boot time gfxmenu and the background image and the font all load as normal. It appears that the tests is /usr/share/grub/grub-mkconfig_lib fail to guess that / will not be accessible at boot time. So if that can't be made smarter, then at least we need a /etc/default/grub option to TELL it. It looks like the rest of the code would do the right thing and automatically copy any wallpapers and fonts to /boot/... and write grub.cfg to refer to those copies instead of the originals if there was just a way to override the automatic detection and tell it that / will not be available. Right now my manual changes get lost every time update-grub runs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615769 Title: fonts should be installed to /boot/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/615769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899244] Re: GMA500 psb_gfx
[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 3.2.0-23-generic-pae on a Vaio P and using psb_gfx and lxde. When I press the bright/dim hot keys lxde (or openbox? x?) recognizes it and displays a little popup showing a brightness change indicator, but the brightness does not actually change. This worked fine on oneiric using emgd 1.8 on the same machine a few weeks ago up until I upgraded to precise beta and switched to psb_gfx. If psb_gfx has backlight support, how do I use it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899244 Title: GMA500 psb_gfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
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 /boot/grub/gfxterm_orig.mod sudo cp gfxterm.mod /boot/grub/gfxterm.mod reboot enjoy no more black border in gfxterm -- 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
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 just use a live usb thumb drive if all else fails of course. ** Attachment added: gfxterm.mod https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+attachment/3040063/+files/gfxterm.mod -- 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
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 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
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... -- 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567226] Re: Black Border around Splash Image
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 features near the edges of the image which I can just count them and remove any doubt. I think grub2 gfxterm draws a border over the image but I can't find any setting to contro it. -- 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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 405294] Re: a2dp skips terribly
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 client, no browser or flash. Sometimes fine for one to four songs before it goes all skippy. Disconnecting/reconnecting to ad2p sometimes fixes for a song or a few songs. It's fine indefinitely on headphones, same software and same streaming over wifi. Just for reference the wifi is internal, pci-express connected, ath9k. product: AR928X Wireless Network Adapter (PCI-Express) [168C:2A] vendor: Atheros Communications Inc. [168C] bus info: pci@:02:00.0 logical name: wlan0 version: 01 serial: 00:23:4d:e1:29:f1 width: 64 bits clock: 33MHz -- bkw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: a2dp skips terribly To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 201711] Re: Apple fn key behavior isn't consistent with what's expected
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 manually edit a system startup shell script, _correctly_, _to a moving target_ (name of hid module in sysfs changes in different kernel versions) and all that that implies, instead of in some gnome menu is also inexplicable. I'm using an Apple keyboard on a generic pc running Ubuntu simply because it's a great, and great looking keyboard. The fact that Apple makes this keyboard in no way implies that I want my Linux system to emulate OS/X. Add another vote to the pile that says, regardless of hardware combination (Apple keyboard on generic pc, Apple keyboard as part of Apple laptop or pc) it is most reasonable to expect, and most reasonable to supply, Linux behavior on Linux! -- Apple fn key behavior isn't consistent with what's expected https://bugs.launchpad.net/bugs/201711 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 435618] Re: [karmic] n-m overwrites /etc/resolv.conf even when NICs are configured in /etc/network/interfaces
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 reach the machine from outside.) Unfortunately as this is just a desktop I pay very little attention to it and I don't remember the exact history and can't say exactly what I did originally and what I did subsequently and what changed when it wasn't supposed to over the last couple years. I can't say for sure that I didn't use nm to configure the static ip. I just know that since the in-place upgrade, nm wipes out resolv.conf every boot and the box can not resolve names until I rewrite it, and for some reason the nic was renamed from eth1 to eth2 and there is no eth 1 or 0. nm displays two connections ifupdown (eth1) , and Auto eth2. eth0 is not displayed anywhere but references to it still exist in config files. I'm pretty sure eth0 was a physically different nic that was replaced long ago. No hardware change of any sort happened before, during or after the dist upgrade. Physically there is only one nic ifconfig -a shows only eth2, lo, and vboxnet0 /etc/network has: interfaces: ---tof--- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth1 inet static address 10.0.0.80 netmask 255.255.255.0 gateway 10.0.0.208 auto eth1 ---eof--- interfaces.bak-0 ---tof--- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp ---eof--- I never manually edited those files. I didn't even know that's where ubuntu stored such things until reading this thread. (I only use ubuntu on a few desks and portables, my servers are all opensuse, so when it comes to the types of machines I use ubuntu on, I am pretty much like any illiterate user, or at least I _want_ to be.) Digressing but while writing this, I disabled networking from the gnome network manager taskbar applet, and and now, for the life of me I can not figure out how to re-enable it (without going behind the scenes and manually running ip or ifconfig route as root) System Preferences Network Connections displays the connections (a bogus eth1 and the new eth2) and lets me edit the ip settings, but does not activate the connection, even when toggling the connect-automatically box. What is a regular user supposed to do, reboot? Logout of gnome back in? Never ever touch that disable button that's sitting there so easy to press? Why doesn't the thing that looks like it's supposed to operate the network connections do so? Or if it actually does, then why couldn't a person who knows how to do it the hard way with ip/ifconfig/route (in any number of unix and unix-like OS's btw) figure it out? That has to be one of those hundred annoyances... -- [karmic] n-m overwrites /etc/resolv.conf even when NICs are configured in /etc/network/interfaces https://bugs.launchpad.net/bugs/435618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 201887] Re: Slim USB Apple Keyboard not working correctly when pressing the numlock key
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 just generates warnings but still works. change: instead of hid or usbhid, now it's hid_apple change: instead of pb_fnmode, now it's fnmode. addition: aside from rc.local and modprobe.d/some file, you may also use /etc/sysfs.conf -- bkw -- Slim USB Apple Keyboard not working correctly when pressing the numlock key https://bugs.launchpad.net/bugs/201887 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
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 point though where opposing points of view are both logical and correct I am of the camp that says, stress test things and push things to their limit regularly and expose any weaknesses as soon and as often as possible, rather than let them accumulate. You suffer the occasional failure at your own hand this way, which seems stupid. If you hadn't touched it, it'd still be running. But I say I'd rather a thing fail on my schedule than on it's own unpredictable one. My boss is the exact opposite. He would leave things alone and carefully avoid bumping anything and he would write a program that trieds to do a given action 10 times to make sure it worked once, rather than hunt down why it might be unreliable and design a proper scheme to make the operation atomic. He considers the brute force or shotgun approach to be a form of reliability ala belt suspenders. I almost can't disagree because outwardly theres no getting around the fact that the shotgun based system often keeps chugging along where the right system halts. So, Windows is like my boss. Undeniably effective, but better? Personally no matter that I understand the practical aspects, I still just can't make myself do anything but reject that way of going about things. It's sort of.. ignorant? short sighted? destructive? It's like solving permissions problems by chmod -R 777 everything in sight. -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
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 that device,
it's definitely going to fail a lot and I'm actually surprised it ever works
except by chance.
The guy who put * in place of that number probably always works, although it's
trying to do way more than you want.
I made a script and triggered it from udev as per the latest hints by comparing
the model name as well as vendor.
I put all the available %codes on the command line and had the script create a
unique temp file by pid and wrote the commandline and the environment to the
file like so:
-
L=/tmp/udev_fix_usb_hd.$$
echo $@ $L
date $L
set $L
-
That produces lots of interesting info.
The first interesting thing is, it runs 3 times for each time the usb cable is
connected.
The contents of the debug files is different each time as the device gets
recognized by different layers and goes from initially being a scsi_device,
then becomes a scsi_generic, then finally becomes a scsi_disk
here is the output of a sample plug-in event.
watch the values for %k
In this case character 3 of %k was never correct for the way it's used in the
script above.
However we can see what is correct, and we don't have to use expr to extract it
from something else either.
Each pass is the interesting parts of one temp file. All 3 files were part of
the same event.
They are shown in the order they happened chronologically. They all happened in
the same second, but the pid numbers in the filenames and the $PPID values
inside the files seem to bear it out.
The udev rule was 91-fix_usb_hd :
SUBSYSTEMS==scsi, ATTRS{vendor}==Seagate, ATTRS{model}==FreeAgentDesktop,
RUN+=/sbin/fix_usb_hd %%k='%k' %%n='%n' %%p='%p' %%b='%b' %%M='%M' %%m='%m' %%P
='%P' %%r='%r' %%N='%N'
The script used I already showed above.
I manually broke the %codes into separate lines for easier reading, and
the variables shown are just the ones that are in any way interesting or
came from udev. stuff like TERM etc.. I left out, but only stuff like
that. So when you see a variable in one block and not in another, it's
because it really wasn't there.
== pass 1
%k='16:0:0:0'
%n='0'
%p='/class/scsi_device/16:0:0:0'
%b='16:0:0:0'
%M='0'
%m='0'
%P=''
%r='/dev'
%N='/dev/.tmp-0-0'
DEVPATH=/class/scsi_device/16:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
PHYSDEVPATH=/devices/pci:00/:00:1d.7/usb1/1-1/1-1:1.0/host16/target16:0:0/16:0:0:0
SUBSYSTEM=scsi_device
UDEVD_EVENT=1
== pass 2
%k='sg6'
%n='6'
%p='/class/scsi_generic/sg6'
%b='sg6'
%M='21'
%m='6'
%P=''
%r='/dev'
%N='/dev/.tmp-21-6'
DEVNAME=/dev/sg6
DEVPATH=/class/scsi_generic/sg6
MAJOR=21
MINOR=6
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
PHYSDEVPATH=/devices/pci:00/:00:1d.7/usb1/1-1/1-1:1.0/host16/target16:0:0/16:0:0:0
SUBSYSTEM=scsi_generic
UDEVD_EVENT=1
== pass 3
%k='sdh'
%n=''
%p='/block/sdh'
%b='sdh'
%M='8'
%m='112'
%P=''
%r='/dev'
%N='/dev/.tmp-8-112'
DEVLINKS='/dev/disk/by-id/usb-Seagate_FreeAgentDesktop_9QG00QCQ/dev/disk/by-path/pci-:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
/dev/disk/by-uuid/07d6ac11-e314-46a2-8d9e-0ebabb98ef19
/dev/disk/by-label/BACKUPS'
DEVNAME=/dev/sdh
DEVPATH=/block/sdh
ID_BUS=usb
ID_FS_LABEL=BACKUPS
ID_FS_LABEL_SAFE=BACKUPS
ID_FS_TYPE=ext2
ID_FS_USAGE=filesystem
ID_FS_UUID=07d6ac11-e314-46a2-8d9e-0ebabb98ef19
ID_FS_VERSION=1.0
ID_MODEL=FreeAgentDesktop
ID_PATH=pci-:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
ID_REVISION=100D
ID_SERIAL=Seagate_FreeAgentDesktop_9QG00QCQ
ID_TYPE=disk
ID_VENDOR=Seagate
MAJOR=8
MINOR=112
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
PHYSDEVPATH=/devices/pci:00/:00:1d.7/usb1/1-1/1-1:1.0/host16/target16:0:0/16:0:0:0
SUBSYSTEM=block
UDEVD_EVENT=1
Notice, the only time character 3 of %k was even a number, it wasn't the right
number for how the script earlier in this thread tries to use it. The right
number in this case would be 16. the other two times the script would have
tried to use a :, and an h.
So, from all that I distill 2 possible scripts that work. Well, one script, two
modes of operation, user selectable.
One that sets allow_restart, and allows the drive to go to sleep.
and one that uses sdparm to disable the standby timer, and does not allow the
drive to go to sleep.
Although we have that nice 16:0:0:0 value right there in several forms
in pass 2, at that point the device is not yet a scsi_disk and so there
is no /sys/class/scsi_disk for it yet. it's there practically at the
same time, but we can't count on that. So in pass 3 it is still possible
to clip it out of another variable by a little shell syntax since it
happens to be right at the end of the value with a nice easy character
to use for splitting...
slosh:~ #
PHYSDEVPATH=/devices/pci:00/:00:1d.7/usb1/1-1/1-1:1.0/host16/target16:0:0/16:0:0:0
slosh:~ # echo
[Bug 61235] Re: USB mass storage stops working after a while
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. I just found this possible solution that uses sdparm to turn off the spindown feature. (it's one of the posts in the middle, search for sdparm) http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16822148235SortField=0SummaryType=0Pagesize=10SelectedRating=-1Page=4 The poster's cutpaste got munged by the web site (html consolidating all whitespace) But this is what he said, unwrapped: code Ensure you have the sdparm utility installed, then, as root, do: # sdparm -al /dev/sdd /dev/sdd: Seagate FreeAgentDesktop 100D Direct access device specific parameters: WP=0 DPOFUA=0 Power condition [po] mode page: IDLE 0 [cha: n, def: 0, sav: 0] Idle timer active STANDBY 1 [cha: y, def: 1, sav: 1] Standby timer active ICT 0 [cha: n, def: 0, sav: 0] Idle condition timer (100 ms) SCT 9000 [cha: y, def:9000, sav:9000] Standby condition timer (100 ms) # sdparm --clear STANDBY -6 /dev/sdd /dev/sdd: Seagate FreeAgentDesktop 100D # sdparm -al /dev/sdd /dev/sdd: Seagate FreeAgentDesktop 100D Direct access device specific parameters: WP=0 DPOFUA=0 Power condition [po] mode page: IDLE 0 [cha: n, def: 0, sav: 0] Idle timer active STANDBY 0 [cha: n, def: 1, sav /code You have to know which device your drive will be (/dev/sdc, /dev/sdd, etc...) so I don't know how to make it automatic except if you just never unplug it or move it or do anything else that would cause it to get assigned a different device name. That matters because of something else I found myself. At least in my case, I do not have to reboot to make the drive work again. I do have to disconnect the usb cable wait a few seconds and the reconnect. The drive comes back alive, but on a new device node. When it's plugged in at boot, it gets /dev/sdc. When I disconnect/reconnect, it gets /dev/sdh. When the drive locks up, it is not possible to umount the filesystem or do anything to that device or that filesystem. After disconnect/reconnect it is possible to umount the filesystem and then mount again on the new device. It will take a while before I can say if it solves the problem for me or not but figured I'd relay it right away since it's something that hasn't been mentioned in this thread yet and some people still have the problem after all the proposals that have been mentioned so far. Another poster later in that thread on newegg claims this worked for him too. Also a question about the udev rules, Am I really reading those right that they basically say if you detect a device by vendor foo on scsi, then do this to it Isn't that assuming a lot? In my case, vendor is Seagate, so, what happens on one of my servers that has 10 or 12 seagate scsi disks? (yes I actually have several of those, and yes I actually was going to use this usb enclosure to move large hunks of data around once in a while, though luckily I never chanced to do that before encountering this problem at home where it didn't matter - phew!) I still need to try one of the fixes proposed here (since I only found this thread today). It seems to me, if possible I would rather have this drive spin down like it wants to, and have the kernel know enough to wait for it, rather than force the drive to run 100%. Since this drive is in fact idle 99% of the time. So the allow_restart sounds like the better answer if it works. Testing ensues. Report follows. Thanks for all the clues and possible answers people have dropped here for me to find. -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
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 sdparm command on /dev/sdh, then did a full system rsync backup of about 300 gigs from a software sata raid0 array to the FreeAgent, which is formatted ext2. I've also done other massive backups to the device like pumping the output of star right to the raw device treating it like a tape. To me that as good as proves I don't have a lots of traffic problem. Then the drive has been untouched for several hours after that backup completed and now I just tried and it's up working fine. To me that says I no longer have the drive turns off problem. So now I will test the allow_restart possible fix to allow the drive to spin down and spin up gracefully instead of just forcing it to stay spinning all the time. That, with the better udev rule would be the ideal. This enclosure is not one you can swap out drive or fan without basically destroying it, so best to just let it go idle as much as possible. Thanks again. bkw -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
