[Bug 1961546] Re: init freezes when >1 display connected on rocket lake PC
Original problem continues with kernel 5.15.0-23, but there is more than a screenful of fb output in what appears to be 1024x768 mode before lockup on switch to i915. Xorg is working normally with only one connected display. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Re: init freezes when >1 display connected on rocket lake PC
Problem is worse with kernel 5.15.0-22, while in distros providing 5.16.11+ and 5.17 kernels the problem is gone. Now in 5.15.0-22, no video ever shows up after the Grub selection is made. The PC apparently hard locks immediately with black screen when two displays are connected, even when only one is powered on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562410/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562409/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562408/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562407/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562406/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562405/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562404/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562403/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562402/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562401/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562400/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562399/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562398/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562397/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Re: init freezes when >1 display connected on rocket lake PC
apport information ** Tags added: apport-collected ** Description changed: # apt-cache policy linux-image-5.15.0-18-generic linux-image-5.15.0-18-generic: Installed: 5.15.0-18.18 Candidate: 5.15.0-18.18 Version table: *** 5.15.0-18.18 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 To reproduce: try to boot with more than one connected display on Intel Rocket Lake PC (e.g. Asus B560-M with i5-11400) Actual results: init stops around the time KMS should engage Expected results: boots normally Upstream bugs fixed: https://gitlab.freedesktop.org/drm/intel/-/issues/4762 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006166 fixed in 5.16.10 & 5.17rc4 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu77 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D17p', '/dev/snd/pcmC0D16p', '/dev/snd/pcmC0D15p', '/dev/snd/pcmC0D14p', '/dev/snd/pcmC0D13p', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller + Bus 001 Device 004: ID 046d:c404 Logitech, Inc. TrackMan Wheel + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUS System Product Name + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=tm8p17ub2204 noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 video=1440x900@60 5 + ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-18-generic N/A + linux-backports-modules-5.15.0-18-generic N/A + linux-firmware 20220217.git6342082c-0ubuntu1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy + Uname: Linux 5.15.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 10/27/2021 + dmi.bios.release: 12.3 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1203 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME B560M-A + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1203:bd10/27/2021:br12.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB560M-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1961546/+attachment/5562396/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] [NEW] init freezes when >1 display connected on rocket lake PC
Public bug reported: # apt-cache policy linux-image-5.15.0-18-generic linux-image-5.15.0-18-generic: Installed: 5.15.0-18.18 Candidate: 5.15.0-18.18 Version table: *** 5.15.0-18.18 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 To reproduce: try to boot with more than one connected display on Intel Rocket Lake PC (e.g. Asus B560-M with i5-11400) Actual results: init stops around the time KMS should engage Expected results: boots normally Upstream bugs fixed: https://gitlab.freedesktop.org/drm/intel/-/issues/4762 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006166 fixed in 5.16.10 & 5.17rc4 ** 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/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949775] Re: System is unusable (crashes) after screen is turned off and afk system must then be hard rebooted to recover.
Reporter has history leading up to this report on https://www.linuxquestions.org/questions/linux-hardware-18/unable-to- use-twin-monitors-4175702792/ where no solution was found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949775 Title: System is unusable (crashes) after screen is turned off and afk system must then be hard rebooted to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1949775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Broken panning, Bug 77321 , got a downstream fix 5 months ago in https://bugzilla.opensuse.org/show_bug.cgi?id=771521 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Broken panning, Bug 77321 , got a downstream fix 5 months ago in https://bugzilla.opensuse.org/show_bug.cgi?id=771521 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589485]
(In reply to Michal Suchanek from comment #26) > This seems to work for me. Are you sure nothing is setting DPI explicitly or implicitly, such as your DE? > X.Org version: 1.17.2 > resolution:100x100 dots per inch > Actual resolution seems to be more like 109 dpi but it's certainly not fixed > at 96. Using which video driver? All FOSS driver versions I've used since long before this bug was opened force 96 unless unless explicitly overridden via xrandr, Xft.dpi, server startup option -dpi, DE settings (which typically use Xft.dpi or xrandr), or xorg.conf*'s DisplaySize option. All these options force a specific DPI. None enable the server or driver to do what computers do best, calculate and apply an accurate value automatically, which is what this bug is effectively requesting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437589] [NEW] boxdraw characters corrupt unless unicode_start is run before starting mc
Public bug reported: en_US installation via HTTP onto test system initiated by Grub loading installation kernel initrd with 'tasks=standard' roughly 30 hours ago, then mc, sddm and selected KDE/KDF packages added via apt*. DISTRIB_DESCRIPTION=Ubuntu Vivid Vervet (development branch) VERSION=15.04 (Vivid Vervet) Linux gx62b 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23 16:25:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux /proc/cmdline tail: root=/dev/sda22 ro ipv6.disable=1 noresume splash=0 vga=791 video=1440x900@60 fbset output: mode 1440x900 geometry 1440 900 1440 900 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode To reproduce: 1-start mc 3:4.8.13-3 on any of tty1-6 without having run unicode_start since booting Actual behavior: 1-boxdraw characters are drawn with wrong characters 2-normal operation output is corrupted by random characters drawn in various places 3-various screen drawing areas do not get refreshed after normal activity Expected behavior: 1-box characters drawn where and as they belong 2-random characters do not appear in diverse places 3-screen areas refreshed after normal operations Notes: 1-Cmdline is as it is because it's what is required to get boot messages and tty output to display in optimal video mode with 16:10 (41cm x 26cm) display that reports incorrect native mode. 1440x900 is its only supported mode with a matching aspect ratio. 2-https://bugzilla.redhat.com/show_bug.cgi?id=458362 seems to discuss same or closely similar issues, and maybe https://bugzilla.opensuse.org/show_bug.cgi?id=780516 and/or https://bugzilla.opensuse.org/show_bug.cgi?id=750326 too. ** Affects: mc (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/1437589 Title: boxdraw characters corrupt unless unicode_start is run before starting mc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mc/+bug/1437589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437589] Re: boxdraw characters corrupt unless unicode_start is run before starting mc
Mc exposes the failure, doesn't cause the failure. AFAICT, the failure is in console-setup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437589 Title: boxdraw characters corrupt unless unicode_start is run before starting mc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mc/+bug/1437589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437589] Re: boxdraw characters corrupt unless unicode_start is run before starting mc
I tried to paste console-setup 1.108ubuntu4 from bug.apport into the package name field during report composition, but it was rejected. I changed it to simply console-setup, but where that went I have no idea. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437589 Title: boxdraw characters corrupt unless unicode_start is run before starting mc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mc/+bug/1437589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
(In reply to comment #53) Probably this bug has been marked invalid because there is a mix of two bugs here: one is related to panning (which I do not know if it's fixed or no), and the other one to mouse constraints when scaling This bug has not been marked invalid. I have X.Org X Server 1.14.5 , and if I issue xrandr --output LVDS1 --scale 2x2 the screen scales correctly, but then the mouse is restricted to the (original 1x1 viewport) upper left quarter of the screen, making the scaling completely unuseful. That's why the summary says doesn't work. Unuseful and doesn't work are functionally equivalent ways of saying it is broken (constrained mouse) and thus not providing function (able to reach all areas of screen with mouse) that makes it usable (can't click mixer icon on panel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
(In reply to comment #53) Probably this bug has been marked invalid because there is a mix of two bugs here: one is related to panning (which I do not know if it's fixed or no), and the other one to mouse constraints when scaling This bug has not been marked invalid. I have X.Org X Server 1.14.5 , and if I issue xrandr --output LVDS1 --scale 2x2 the screen scales correctly, but then the mouse is restricted to the (original 1x1 viewport) upper left quarter of the screen, making the scaling completely unuseful. That's why the summary says doesn't work. Unuseful and doesn't work are functionally equivalent ways of saying it is broken (constrained mouse) and thus not providing function (able to reach all areas of screen with mouse) that makes it usable (can't click mixer icon on panel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Since panning at least can work via xrandr, I've forked the failure of xorg.con* to provide equivalent panning function of xrandr without arbitrary mouse constraint to bug 77321 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Since panning at least can work via xrandr, I've forked the failure of xorg.con* to provide equivalent panning function of xrandr without arbitrary mouse constraint to bug 77321 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Panning works via xrandr (only; not via xorg.con*) also in Kubuntu 12.04's server 1.11.4, while scaling does fail by having the mouse cursor bound within the screen mode's size. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Panning works via xrandr (only; not via xorg.con*) also in Kubuntu 12.04's server 1.11.4, while scaling does fail by having the mouse cursor bound within the screen mode's size. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
As the summary is currently written, this bug is INVALID. Panning works at least as far back as 1.13.2-1.21.1.i586 in openSUSE 12.3 (i865G,rv200), in addition to current 1.15.x and 1.16rc1 servers in Fedora, Mageia, and openSUSE, but only when xrandr is used to configure it. Configuration via /etc/X11/xorg.con* files and syntax that worked in older servers such as 1.10.4 is what is broken for ATI, Intel and NVidia. I haven't tested scaling except briefly, and successfully, via xrandr only, in e.g. 1.16rc1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
As the summary is currently written, this bug is INVALID. Panning works at least as far back as 1.13.2-1.21.1.i586 in openSUSE 12.3 (i865G,rv200), in addition to current 1.15.x and 1.16rc1 servers in Fedora, Mageia, and openSUSE, but only when xrandr is used to configure it. Configuration via /etc/X11/xorg.con* files and syntax that worked in older servers such as 1.10.4 is what is broken for ATI, Intel and NVidia. I haven't tested scaling except briefly, and successfully, via xrandr only, in e.g. 1.16rc1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
For well over a week I've been first testing the success of panning for various combinations of gfxcard, monitor and fb size in servers prior to the changes resulting in this bug report and then same for installations to which I've updated using the 94929 patch applied by Tobias Klausmann in the openSUSE build-service. Initially the only recording I did of my testing I reported here. After while I began recording in the form of screenshots accompanied by the Xorg.#.log associated with each one. These are available for perusal at http://fm.no-ip.com/SS/Xorg/ . Among them is one instance of a scaling test, 1.2x1.2 applied to a 1440x900 screen. The largest fb size I tested was 3840x2400. The newest gfxchip used was a Intel 4000 series (G41). Others used are nv11, G84, rv200, rv250, rv380, i865G, i915G i945G. The highest resolution used was 1920x1080. Total success pairs there currently is 31, of which 14 are pre-bug and 17 are server 1.16rc1. KDE3 KDE4 dominate the DEs represented. A few are IceWM and Lxde. The only outright failure so far was on i945G and 1.16rc1 on both openSUSE 13.1 13.2, but after another system/xorg updates round those inexplicable failures apparently solved themselves. Among the overwhelming number of successes are many instances of various forms of painting and mouse pointer trouble among the configurations with the largest panning areas that always goes away if panning is disabled. However, such problems are common to both old servers and DEs as well as current ones. The painting problems don't show up in any of the screenshots. Except for the comment 44 reported failure of xorg.conf* to produce expected results, WRT to bounds and sizes at least, the 94929 patch seems to be doing what it needs to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
For well over a week I've been first testing the success of panning for various combinations of gfxcard, monitor and fb size in servers prior to the changes resulting in this bug report and then same for installations to which I've updated using the 94929 patch applied by Tobias Klausmann in the openSUSE build-service. Initially the only recording I did of my testing I reported here. After while I began recording in the form of screenshots accompanied by the Xorg.#.log associated with each one. These are available for perusal at http://fm.no-ip.com/SS/Xorg/ . Among them is one instance of a scaling test, 1.2x1.2 applied to a 1440x900 screen. The largest fb size I tested was 3840x2400. The newest gfxchip used was a Intel 4000 series (G41). Others used are nv11, G84, rv200, rv250, rv380, i865G, i915G i945G. The highest resolution used was 1920x1080. Total success pairs there currently is 31, of which 14 are pre-bug and 17 are server 1.16rc1. KDE3 KDE4 dominate the DEs represented. A few are IceWM and Lxde. The only outright failure so far was on i945G and 1.16rc1 on both openSUSE 13.1 13.2, but after another system/xorg updates round those inexplicable failures apparently solved themselves. Among the overwhelming number of successes are many instances of various forms of painting and mouse pointer trouble among the configurations with the largest panning areas that always goes away if panning is disabled. However, such problems are common to both old servers and DEs as well as current ones. The painting problems don't show up in any of the screenshots. Except for the comment 44 reported failure of xorg.conf* to produce expected results, WRT to bounds and sizes at least, the 94929 patch seems to be doing what it needs to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Via xrandr, 94929 patch also tested working apparently OK for: ATI rv380 VGA DVI ports 1680x1050 on 1280x1024 Intel G41 VGA HDMI ports 1680x1050 on 1280x1024 Nouveau G84 DVI port 1680x1050 on 1280x1024. with without DVI-to-VGA adapter Nouveau G84 DVI port 2048x1152 2560x1600 3840x2160 on 1440x900 with DVI-to-VGA adapter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Via xrandr, 94929 patch also tested working apparently OK for: ATI rv380 VGA DVI ports 1680x1050 on 1280x1024 Intel G41 VGA HDMI ports 1680x1050 on 1280x1024 Nouveau G84 DVI port 1680x1050 on 1280x1024. with without DVI-to-VGA adapter Nouveau G84 DVI port 2048x1152 2560x1600 3840x2160 on 1440x900 with DVI-to-VGA adapter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
With the g84 on 1080 HDTV, apparently scaling, which I never tried before, is working too: $ xrandr --output DVI-I-1 --scale 1.2x1.2 (Assorted X data collected via script): # grep PRETTY /etc/os-release PRETTY_NAME=openSUSE 13.2 Milestone 0 (Harlequin) (x86_64) # head -n16 /var/log/Xorg.0.log (beta warning stripped) [31.305] X.Org X Server 1.15.99.901 (1.16.0 RC 1) Release Date: 2014-02-24 [31.305] X Protocol Version 11, Revision 0 [31.305] Build Operating System: openSUSE SUSE LINUX [31.305] Current Operating System: Linux big41 3.14.0-rc7-1-desktop #1 SMP PREEMPT Thu Mar 20 12:43:03 UTC 2014 (89fa272) x86_64 [31.305] Kernel command line: root=LABEL=os132h50 ipv6.disable=1 net.ifnames=0 noresume splash=verbose vga=791 video=1024x768@60 # grep Output /var/log/Xorg.0.log | egrep -v 'disconnected|no monitor' [31.653] (II) NOUVEAU(0): Output DVI-I-1 connected [31.653] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1080 # grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep DisplaySize grep: /etc/X11/xorg.conf.d/50-monitor.conf: no such file or directory # grep -v ^\# /etc/X11/xorg.conf | grep DisplaySize grep: /etc/X11/xorg.conf: no such file or directory # grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep PreferredMode grep: /etc/X11/xorg.conf.d/50-monitor.conf: no such file or directory # grep -v ^\# /etc/X11/xorg.conf | grep PreferredMode # xrdb -query | grep dpi grep: /etc/X11/xorg.conf: no such file or directory # xdpyinfo | egrep 'dime|ution' dimensions:2304x1296 pixels (608x342 millimeters) resolution:96x96 dots per inch # xrandr | head Screen 0: minimum 320 x 200, current 2304 x 1296, maximum 8192 x 8192 DVI-I-1 connected 2304x1296+0+0 (normal left inverted right x axis y axis) 698mm x 393mm 1920x1080 60.0*+ 60.0 59.9 24.0 24.0 1920x1080i 60.1 60.0 1280x720 60.0 59.9 1024x768 75.1 70.1 60.0 DVI-I-2 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
With the g84 on 1080 HDTV, apparently scaling, which I never tried before, is working too: $ xrandr --output DVI-I-1 --scale 1.2x1.2 (Assorted X data collected via script): # grep PRETTY /etc/os-release PRETTY_NAME=openSUSE 13.2 Milestone 0 (Harlequin) (x86_64) # head -n16 /var/log/Xorg.0.log (beta warning stripped) [31.305] X.Org X Server 1.15.99.901 (1.16.0 RC 1) Release Date: 2014-02-24 [31.305] X Protocol Version 11, Revision 0 [31.305] Build Operating System: openSUSE SUSE LINUX [31.305] Current Operating System: Linux big41 3.14.0-rc7-1-desktop #1 SMP PREEMPT Thu Mar 20 12:43:03 UTC 2014 (89fa272) x86_64 [31.305] Kernel command line: root=LABEL=os132h50 ipv6.disable=1 net.ifnames=0 noresume splash=verbose vga=791 video=1024x768@60 # grep Output /var/log/Xorg.0.log | egrep -v 'disconnected|no monitor' [31.653] (II) NOUVEAU(0): Output DVI-I-1 connected [31.653] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1080 # grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep DisplaySize grep: /etc/X11/xorg.conf.d/50-monitor.conf: no such file or directory # grep -v ^\# /etc/X11/xorg.conf | grep DisplaySize grep: /etc/X11/xorg.conf: no such file or directory # grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep PreferredMode grep: /etc/X11/xorg.conf.d/50-monitor.conf: no such file or directory # grep -v ^\# /etc/X11/xorg.conf | grep PreferredMode # xrdb -query | grep dpi grep: /etc/X11/xorg.conf: no such file or directory # xdpyinfo | egrep 'dime|ution' dimensions:2304x1296 pixels (608x342 millimeters) resolution:96x96 dots per inch # xrandr | head Screen 0: minimum 320 x 200, current 2304 x 1296, maximum 8192 x 8192 DVI-I-1 connected 2304x1296+0+0 (normal left inverted right x axis y axis) 698mm x 393mm 1920x1080 60.0*+ 60.0 59.9 24.0 24.0 1920x1080i 60.1 60.0 1280x720 60.0 59.9 1024x768 75.1 70.1 60.0 DVI-I-2 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Created attachment 96397 Xorg.0.log from i915 host gx280 having used xrandr to produce panning from 94929 patch This seems to be unusually verbose for the brief time X was running, with few apps opened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Comment 43 applies to use of xorg.conf in attempting to produce desired X configuration, e.g. xorg.conf for Intel gfx containing: Section Device Identifier Default Device Option monitor-VGA1 Default Monitor EndSection Section Monitor Identifier Default Monitor Option DPMS off DisplaySize 405 253 # 120 DPI @ 1920x1200 virtual Option PreferredMode 1440x900 Option Panning 1920x1200 EndSection Section Screen Identifier Default Screen Device Default Device Monitor Default Monitor EndSection produces expected results for server 1.9.3, but not for server 1.16.0RC1. Functional panning matching that produced by the above xorg.conf can be at least mostly achieved in i915 via xrandr as follows: xrandr --dpi 120 --fb 1920x1200 --output VGA1 --mode 1440x900 --panning 1920x1200 or xrandr --fbmm 405x253 --fb 1920x1200 --output VGA1 --mode 1440x900 --panning 1920x1200 A remaining problem therefore exists that did not exist prior to the server changes made that made this bug report necessary in the first place, that xorg.conf no longer does what xrandr can, as xorg.conf used to be able to do. This is new with the 96204 patch, as with the 56408 patch and server 1.12.3, xorg.conf gets the job done as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Created attachment 96397 Xorg.0.log from i915 host gx280 having used xrandr to produce panning from 94929 patch This seems to be unusually verbose for the brief time X was running, with few apps opened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Comment 43 applies to use of xorg.conf in attempting to produce desired X configuration, e.g. xorg.conf for Intel gfx containing: Section Device Identifier Default Device Option monitor-VGA1 Default Monitor EndSection Section Monitor Identifier Default Monitor Option DPMS off DisplaySize 405 253 # 120 DPI @ 1920x1200 virtual Option PreferredMode 1440x900 Option Panning 1920x1200 EndSection Section Screen Identifier Default Screen Device Default Device Monitor Default Monitor EndSection produces expected results for server 1.9.3, but not for server 1.16.0RC1. Functional panning matching that produced by the above xorg.conf can be at least mostly achieved in i915 via xrandr as follows: xrandr --dpi 120 --fb 1920x1200 --output VGA1 --mode 1440x900 --panning 1920x1200 or xrandr --fbmm 405x253 --fb 1920x1200 --output VGA1 --mode 1440x900 --panning 1920x1200 A remaining problem therefore exists that did not exist prior to the server changes made that made this bug report necessary in the first place, that xorg.conf no longer does what xrandr can, as xorg.conf used to be able to do. This is new with the 96204 patch, as with the 56408 patch and server 1.12.3, xorg.conf gets the job done as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Created attachment 96204 Xorg.0.log from 92915G host gx280 http://download.opensuse.org/repositories/home:/tobijk:/X11:/XOrg/openSUSE_Factory/i586/ ostensibly has the attachment 94929 patch applied, which I installed on nv11, rv250 and i915G systems running X.Org X Server 1.15.99.901. # rpm -q --changelog xorg-x11-server | head -n8 * Fri Mar 21 2014 tobias.johannes.klausmann@... - Add patch u_randr_account_for_panning_and_transform_when_creating_cursor.patch (patch230) (BNC#771521), (FDO#39949) I could not detect any difference before or after installing the xorg-x11-server version 7.6_1.15.99.901.8-393.1 that includes the patch, plus its dependencies. IOW, pointer could not reach right or bottom screen edges before or after installing with any of the ati, intel or nouveau drivers. Ati and nouveau test logs are available on request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Created attachment 96204 Xorg.0.log from 92915G host gx280 http://download.opensuse.org/repositories/home:/tobijk:/X11:/XOrg/openSUSE_Factory/i586/ ostensibly has the attachment 94929 patch applied, which I installed on nv11, rv250 and i915G systems running X.Org X Server 1.15.99.901. # rpm -q --changelog xorg-x11-server | head -n8 * Fri Mar 21 2014 tobias.johannes.klausmann@... - Add patch u_randr_account_for_panning_and_transform_when_creating_cursor.patch (patch230) (BNC#771521), (FDO#39949) I could not detect any difference before or after installing the xorg-x11-server version 7.6_1.15.99.901.8-393.1 that includes the patch, plus its dependencies. IOW, pointer could not reach right or bottom screen edges before or after installing with any of the ati, intel or nouveau drivers. Ati and nouveau test logs are available on request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
It seems clear that at least analog hardware users who require panning and want or need to stick to FOSS solutions need to stick to out of support Xorg versions and/or out of support drivers, and/or ancient gfxchip technology (e.g. MGA), and/or cheap (and usually slow) hardware (e.g. # XGI Technology Inc. (eXtreme Graphics Innovation) Z7/Z9 (XG20 core), a slug at 24 bit, tolerable at 16 bit as long as not extending the desktop virtually as panning was made to do). It looks like users of supported FOSS software versions and modern competent gfxchips are out of options other than acquiring (digital?) displays big enough, or acquiring additional (digital?) video ports and (digital?) displays, to cover their otherwise virtual needs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
It seems clear that at least analog hardware users who require panning and want or need to stick to FOSS solutions need to stick to out of support Xorg versions and/or out of support drivers, and/or ancient gfxchip technology (e.g. MGA), and/or cheap (and usually slow) hardware (e.g. # XGI Technology Inc. (eXtreme Graphics Innovation) Z7/Z9 (XG20 core), a slug at 24 bit, tolerable at 16 bit as long as not extending the desktop virtually as panning was made to do). It looks like users of supported FOSS software versions and modern competent gfxchips are out of options other than acquiring (digital?) displays big enough, or acquiring additional (digital?) video ports and (digital?) displays, to cover their otherwise virtual needs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589485]
More from that IRC conversation: alesguzik I'm not asking about making it default, but when screen size can be detected and resolution is known, what is the problem with dpi? alesguzik It worked at some point in the past ohsix it never worked Ohsix's definition of never must be different from the dictionary's. As alesguzik said, automatically matching DPI to display density did work in the past: $ cat /etc/SuSE-release openSUSE 10.2 (i586) VERSION = 10.2 $ head -n15 /var/log/Xorg.0.log | tail -n6 X Window System Version 7.1.99.902 (7.2.0 RC 2) Release Date: 13 November 2006 X Protocol Version 11, Revision 0, Release 7.1.99.902 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux m7ncd 2.6.18.8-0.10-default #1 SMP Wed Jun 4 15:46:34 UTC 2008 i686 Build Date: 02 June 2008 $ grep Output /var/log/Xorg.0.log | egrep -v 'disconnected|no monitor' $ grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep DisplaySize grep: /etc/X11/xorg.conf.d/50-monitor.conf: No such file or directory $ grep -v ^\# /etc/X11/xorg.conf | grep DisplaySize $ grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep PreferredMode grep: /etc/X11/xorg.conf.d/50-monitor.conf: No such file or directory $ grep -v ^\# /etc/X11/xorg.conf | grep PreferredMode $ xrdb -query | grep dpi $ xdpyinfo | egrep 'dime|ution' dimensions:1600x1200 pixels (402x302 millimeters) resolution:101x101 dots per inch $ xrandr | head -n5 SZ:Pixels Physical Refresh *0 1600 x 1200 ( 402mm x 302mm ) *85 75 70 65 60 1 1400 x 1050 ( 402mm x 302mm ) 75 60 2 1280 x 960( 402mm x 302mm ) 85 60 3 1152 x 864( 402mm x 302mm ) 75 more Xorg.0.log excerpts: (II) RADEON(0): EDID data from the display on port 1 -- (II) RADEON(0): Manufacturer: NEC Model: 61da Serial#: 5356 (II) RADEON(0): Year: 2002 Week: 39 (--) RADEON(0): Virtual size is 1600x1200 (pitch 1664) (**) RADEON(0): *Default mode 1600x1200: 229.5 MHz, 106.2 kHz, 85.0 Hz (--) RADEON(0): Display dimensions: (400, 300) mm (--) RADEON(0): DPI set to (101, 101) $ xrandr -v Server reports RandR version 1.1 $ cat /etc/SuSE-release openSUSE 10.2 (i586) VERSION = 10.2 $ head -n15 /var/log/Xorg.0.log | tail -n6 X Window System Version 7.1.99.902 (7.2.0 RC 2) Release Date: 13 November 2006 X Protocol Version 11, Revision 0, Release 7.1.99.902 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux m7ncd 2.6.18.8-0.10-default #1 SMP Wed Jun 4 15:46:34 UTC 2008 i686 Build Date: 02 June 2008 $ grep Output /var/log/Xorg.0.log | egrep -v 'disconnected|no monitor' $ grep -v ^\# /etc/X11/xorg.conf | grep DisplaySize $ grep -v ^\# /etc/X11/xorg.conf | grep PreferredMode $ xrdb -query | grep dpi $ xdpyinfo | egrep 'dime|ution' dimensions:1920x1440 pixels (403x302 millimeters) resolution:121x121 dots per inch $ xrandr | head -n5 SZ:Pixels Physical Refresh *0 1920 x 1440 ( 403mm x 302mm ) *75 60 1 1856 x 1392 ( 403mm x 302mm ) 75 60 2 1792 x 1344 ( 403mm x 302mm ) 75 60 3 1600 x 1200 ( 403mm x 302mm ) 85 75 70 65 60 $ xrandr -v Server reports RandR version 1.1 more Xorg.0.log excerpts: (II) RADEON(0): EDID data from the display on port 1 -- (II) RADEON(0): Manufacturer: NEC Model: 61da Serial#: 5356 (II) RADEON(0): Year: 2002 Week: 39 (--) RADEON(0): Virtual size is 1920x1440 (pitch 1920) (**) RADEON(0): *Default mode 1920x1440: 297.0 MHz, 112.5 kHz, 75.0 Hz (--) RADEON(0): Display dimensions: (400, 300) mm (--) RADEON(0): DPI set to (121, 121) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
If it hasn't happened already, the supply of supported distros that feature working panning should be exhausted soon. Is there anything non- programmers can do to facilitate a programmer fixing this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
If it hasn't happened already, the supply of supported distros that feature working panning should be exhausted soon. Is there anything non- programmers can do to facilitate a programmer fixing this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
(In reply to comment #31) http://download.opensuse.org/repositories/home:/bjoernv:/branches:/openSUSE:/ 12.2:/Update/standard/ As indicated in downstream https://bugzilla.novell.com/show_bug.cgi?id=771521 these work for me with Intel 865G and NVidia G84. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
(In reply to comment #31) http://download.opensuse.org/repositories/home:/bjoernv:/branches:/openSUSE:/ 12.2:/Update/standard/ As indicated in downstream https://bugzilla.novell.com/show_bug.cgi?id=771521 these work for me with Intel 865G and NVidia G84. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
(In reply to comment #55) Please use the correct dpi by default. If it doesn't, it's usually: 1-your distro's fault, or 2-your hardware's fault, or 3-your use of unequal DPI multiple displays, which is a complicated problem for X to deal with X automagic configuration will fall back to 96 if there's a problem with your hardware supplying the info automagic needs to work, while many distros force 96, in part because it makes web browsers behave like Windows on a not insignificant number of web sites, and in another part because DTEs are behind the development curve on adapting fonts, icons and initial window sizes to high DPI displays. Resolution independence is needed, but not available, either from most web sites, or most DTE components. OTOH, as long as you're sticking to one display, you can force correct DPI via xrandr, xorg.conf.d/, xorg.conf, xinitrc, proprietary nvidia driver and/or several other documented ways if bothered by inaccurate automagic or distro forcing. If your distro maker is forcing 96, complain to it. Just because xorg.conf is not used by default does not mean you cannot use it to enjoy accurate DPI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
Created attachment 43316 Xorg.0.log from server 1.9.3 using 86x86 DPI on i845G (In reply to comment #57) Isn't this bug precisely about X.org *always ignoring* the hardware DPI value from the EDID? There may have been a time when that was the case, but this was filed by an Intel video user long before KMS was required by the Intel driver. Obviously from the attachment, using no xorg.conf, xrandr, xorg.conf.d/ or anything else to force DPI, always is not the much more recent case. Display used is 20 4:3 1400x1050 Viewsonic several years old. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
Created attachment 43320 86 DPI screenshot What do I win? :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
The bug is marked general, not Intel. Various comments spoke of at least one other chip prior to my MGA comment 58. Before your comment 58 reached my eyes, I had to put that Intel host aside to work on the MGA host, so I used that to demonstrate what I wrote in comment 58, that always is incorrect. That said, I reread comment 6, which does indicate manual intervention via config file or xrandr is normally required to achieve accurate DPI, normal meaning ATI, Intel or NVidia, chips that have current version xrandr-supported drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
Created attachment 45751 120 DPI full 1600x1200 desktop screenshot This demonstrates the current state of elevated actual DTE DPI affairs, as of the release of openSUSE 11.4 about 5 weeks ago. Video chip is rv380. Driver is radeon. 120 DPI is achieved exclusively via DisplaySize in xorg.conf. Note that all apps are using the same font for the UI (urlbars, main menu), but that web browser viewports are of two schools: 1-Those forcing 96 DPI (WebKit in Google Chrome 7.0.517.44 and Epiphany 2.30.6, Opera 11.01) 2-Those using the DTE's DPI. (Gecko pre-rv2.0 in Firefox 3.6.16, KHTML in Konqueror 4.6) Note that Gecko rv2+ also forces to 96 in the usual cases, but provides a workaround (mozmm) that allows pages to size to match DTE DPI, which http://fm.no-ip.com/Auth/Font/font-vera.html in the screenshots does, and means all of Firefox 3.x, SeaMonkey 2.0.x, Firefox 4.x SeaMonkey 2.1x will render it the same if the DTE DPI is 96 or above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
(In reply to comment #77) (Chrome already does so, in a misguided attempt to force a constant ratio between px and pt across all websites. Chrome does because it's built on WebKit, where 96 as the only possibility is the traditional Macintosh way, which became also the Internet Explorer default behavior back in v7 or v8. Firefox still seems to respect the system DPI by default, AFAICT.) Since 2010/08/18 in https://bugzilla.mozilla.org/show_bug.cgi?id=537890 it only does so in the UI, not in web page content, where it now copies the IE, Chrome and Safari insanity. You can see the impact by using it to view both http://fm.no-ip.com/Auth/dpi-screen-windowg.html (old edition that worked as expected before that fix), and http://fm.no- ip.com/Auth/dpi-screen-window.html (modified version that can be accurate only in Geckos, Konq, and most old browsers). Its behavior can be impacted by two hidden preferences, layout.css.dpi (integer) layout.css.devPixelsPerPx (a string parsed as a float), the former of which defaults to -1, and the latter to 1.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
https://bugzilla.novell.com/show_bug.cgi?id=771521 explains how panning works for me using Radeon but not Intel or Nouveau. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
https://bugzilla.novell.com/show_bug.cgi?id=771521 explains how panning works for me using Radeon but not Intel or Nouveau. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
FWIW: I don't try to use randr directly to set up panning. I do it either through xorg.conf or xorg.conf.d/50-monitor.conf because I'm usually controlling DPI via DisplaySize, limiting VertRefresh to 60 or 75, turning DPMS DDC off, and turning DefaultModes on. It would be nice if TargetRefreshRate ever worked. I don't use small displays either. Mostly I use CRTs as described on http://lists.x.org/archives/xorg-devel/2012-June/031652.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
FWIW: I don't try to use randr directly to set up panning. I do it either through xorg.conf or xorg.conf.d/50-monitor.conf because I'm usually controlling DPI via DisplaySize, limiting VertRefresh to 60 or 75, turning DPMS DDC off, and turning DefaultModes on. It would be nice if TargetRefreshRate ever worked. I don't use small displays either. Mostly I use CRTs as described on http://lists.x.org/archives/xorg-devel/2012-June/031652.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
For the record, openSUSE Factory (devel) is currently @ 1.12.2, where panning for me is working OK with radeon/rv200, but not with nouveau or intel drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
For the record, openSUSE Factory (devel) is currently @ 1.12.2, where panning for me is working OK with radeon/rv200, but not with nouveau or intel drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263435]
(In reply to Piyush Soni from comment #557) if HTML5 becomes really popular, it might replace Flash altogether, removing the need of fixing this bug - but I'm sure Adobe will do something to not let that happen so soon... Adobe already started the process of pushing webmasters to stop using Flash. I couldn't find the link I wanted to put here as reference, but here's a related one explaining Adobe will no longer develop Flash for Linux: http://blogs.adobe.com/flashplayer/2012/02/adobe-and-google- partnering-for-flash-player-on-linux.html Please read whiteboard before commenting about age. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263435 Title: Firefox cannot close tab (using Ctrl-w) when flash content is selected on page To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653436] Re: All combinations Shift+F1 to Shift+F8 don't work on mc in console (tty) mode, on konsole (gui) mode works normally
https://bugzilla.novell.com/show_bug.cgi?id=400552 is the same problem in openSUSE and http://mail.gnome.org/archives/mc- devel/2011-May/msg1.html is some mc-devel discussion on the subject. ** Bug watch added: Novell/SUSE Bugzilla #400552 https://bugzilla.novell.com/show_bug.cgi?id=400552 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/653436 Title: All combinations Shift+F1 to Shift+F8 don't work on mc in console (tty) mode, on konsole (gui) mode works normally -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301158]
(In reply to comment #8) It's not usual that setting DPI to a multiple of 12 can produce more pleasing results than prime numbers or multiples of 5. On your display Kyle, 144, a multiple of 12 and exactly 1.5 times 96, might work better than 147 or 145. s/It's not usual/It's not unusual/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/301158 Title: Firefox layout.css.dpi ignored -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301158]
It's not usual that setting DPI to a multiple of 12 can produce more pleasing results than prime numbers or multiples of 5. On your display Kyle, 144, a multiple of 12 and exactly 1.5 times 96, might work better than 147 or 145. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/301158 Title: Firefox layout.css.dpi ignored -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651793] [NEW] native vga=0x120 on cmdline does not work on Intel chips that do not support standard VESA modes
Public bug reported: This seems essentially a continuation of or closely related to https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/150797 In Lucid when I try vga=0x120 on cmdline I do not get the Intel legacy native 132 column by 25 row mode. A message flashes on screen and disappears too quickly to read, and nothing that looks similar is to be found anywhere in /var/log. Googling I've seen references to gfxpayload, but these all seem to imply framebuffer ever worked. Framebuffer never has worked on any i810 video chip I've used. None of the gfxpayload examples I've tried on Lucid work. So, I'm stuck in 80x30 consoles using Lucid, while openSUSE 11.3 (later released) on the same machine gives me the same functional 120X25 consoles I've been using for over a decade. ** Affects: ubuntu Importance: Undecided Status: New -- native vga=0x120 on cmdline does not work on Intel chips that do not support standard VESA modes https://bugs.launchpad.net/bugs/651793 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 150797] Re: Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
This is worksforme as of 9.10. -- Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120 https://bugs.launchpad.net/bugs/150797 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 222256] Re: small fonts in epiphany
I installed Epiphany under Karmic Kubuntu. I see no way evident to directly influence the size of Epiphany web page fonts other than via its minimum size setting or use of zoom. Epiphany does not respond to changes in KDE font settings in any way that I can tell. http://fm.no- ip.com/auth/dpi-screen-window.html and http://fm.no-ip.com/auth/Font /fonts-ptdemo.html are my web pages used in Guilherme's screenshots. -- small fonts in epiphany https://bugs.launchpad.net/bugs/56 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 150797] Re: Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
I no longer use *buntu on any systems where the standard VESA modes do not work as expected. It's possible http://bugzilla.kernel.org/show_bug.cgi?id=7513 may have provided a fix. The Novell bug noted earlier has been marked fixed as well. I do still have a working i810 system, so I need to try a 9.04 live CD when I get a chance, if someone else doesn't get to it and comment here first. ** Bug watch added: Linux Kernel Bug Tracker #7513 http://bugzilla.kernel.org/show_bug.cgi?id=7513 -- Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120 https://bugs.launchpad.net/bugs/150797 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 16186] Re: fails to recognise any partitions when primary partition inside extended partition
The new summary makes my previous comments in this bug inapplicable to this bug. My disk had a standard partition layout, with all logicals inside an extended that logically follows 3 primaries. -- fails to recognise any partitions when primary partition inside extended partition https://bugs.launchpad.net/bugs/16186 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111840] Re: Ubuntu 7.04 Feisty Fawn Console has only one vesafb VGA mode 640x480 on Dell Optiplex GX260
For framebuffer modes other than 80x25 to function, the GX260 BIOS' Onboard Video Buffer usually has to be set to 8MB. Leaving it at the default 1MB usually does not work for the onboard 845G graphics chip. Now in a fresh install of Kubuntu Intrepid 8.10 from the alternate CD, I find vga=0x305, vga=788, vga=0x31a vga=0x317 all give working framebuffer tty[1-6]s. OTOH, regardless whether the grub kernel line contains either splash, nosplash or splash=off, with or without quiet, nothing shows up on the display except a blinking cursor until X/KDM starts, though on Ctrl- Alt-F1 after KDM appears there are init messages preceding the login prompt. Furthermore, actually logging into KDE resulted in a totally locked up system that required power cycling to recover, until after I ran 'apt- get update; apt-get upgrade'. -- Ubuntu 7.04 Feisty Fawn Console has only one vesafb VGA mode 640x480 on Dell Optiplex GX260 https://bugs.launchpad.net/bugs/111840 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 241885] Re: firefox-3.0 default font size, minimum font size broken
*** This bug is a duplicate of bug 118745 *** https://bugs.launchpad.net/bugs/118745 This bug is INVALID, not a dupe of 118745. Firefox is behaving exactly as expected. When you set a default font size in Firefox you're setting the size in px, not pt. The expected pt size for a 10px default font at 94 DPI would indeed be 7.66pt (72 / 94 * 10). If you want a 10pt default font size in Firefox at 94 DPI, you'll need to choose 13 (probably) or 14 (possibly). -- firefox-3.0 default font size, minimum font size broken https://bugs.launchpad.net/bugs/241885 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 78687] Re: [Edgy] Default font in Firefox too big
*** This bug is a duplicate of bug 118745 *** https://bugs.launchpad.net/bugs/118745 This bug is in a sense a DPI issue, but Firefox is behaving as expected, and this bug is not a duplicate of bug 118745. Unlike the rest of a typical X desktop, in which font sizes are set and customized in pt sizes, Firefox defaults are set in px. Firefox's default default is 16px, (shown in default font settings advanced, even though omitted from the initial settings tab) which is designed correspond to 12pt @ a DPI of 96, the DPI used by default in M$ Windows. Because the pt size to px size relationship varies with DPI, it is expected behavior for Firefox defaults to be too big or too small when DPI varies from 96, In this case, your DPI is lower, making 16px too big. For those with high resolution screens, 16px will typically be too small. No fix for bug 118745 can or will change this. A fix for https://bugzilla.mozilla.org/show_bug.cgi?id=414427 or a similar upstream bug for have to be fixed for this problem to go away in default profiles. User solution currently requires manually changing the Firefox default. -- [Edgy] Default font in Firefox too big https://bugs.launchpad.net/bugs/78687 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 88289] Re: Firefox default layout.css.dpi config wrong.
*** This bug is a duplicate of bug 118745 *** https://bugs.launchpad.net/bugs/118745 This bug is not a bug 118745 duplicate. Firefox defaults are set in px, while most of the rest of a normal X desktop are set in pt. The px to pt relationship does vary with DPI, making this look like a DPI bug, but as long as Firefox is behaving as expected, which it is, having X determine and use a correct DPI, bug 118745, will not affect Firefox behavior. Only if and when Firefox is changed upstream to use whatever defaults are set in X instead of using its own individually set default size preferences can this problem go away. -- Firefox default layout.css.dpi config wrong. https://bugs.launchpad.net/bugs/88289 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 178558] Re: Firefox 3.0 makes everything annoyingly huge
*** This bug is a duplicate of bug 118745 *** https://bugs.launchpad.net/bugs/118745 This is not a bug 118745 duplicate. Nothing about getting X to use an appropriate DPI will directly change the Firefox behavior. A good fix for this requires an upstream solution from the folks at mozilla.org. -- Firefox 3.0 makes everything annoyingly huge https://bugs.launchpad.net/bugs/178558 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 134983] Re: Cannot mount /home on /dev/hda16
Leann, the fact that no kernel fix is expected for the foreseeable future is no reason to WONTFIX. A fix will come from somewhere at some point. It's just not entirely clear where it will come from, or when. There has always been a fix available by recompiling the kernel to restore IDE and preload it in initrds, and there is an imminent or existing fix via device mapper and kpartx available for SUSE users: https://bugzilla.novell.com/show_bug.cgi?id=397816 Wontfixing this is like telling upgraders to use SUSE instead. -- Cannot mount /home on /dev/hda16 https://bugs.launchpad.net/bugs/134983 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 150797] Re: Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
That's basically what https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/150797/comments/1 means IIRC. Newer BIOS may have a 1MB/8MB option while older BIOS have only .5MB/1MB options. IIRC, my GX150 i815 with Hardy has a BIOS with .5/1 option set to 1, while my Intel DLVA 845G with Hardy has the 1/8 option set to 8. I don't believe the other bug describes a workaround as much as it does full VESA support vs. partial VESA support in the motherboard BIOS, with full VESA support available only when there is an 8M BIOS option. On the systems with the 8M option available, the 0x120 mode does not work but the standard VESA modes do work; while on those with only .5/1 options, no standard VESA modes work, and 0x120 does. see also https://bugzilla.novell.com/show_bug.cgi?id=259577 and https://qa.mandriva.com/show_bug.cgi?id=39837 -- Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120 https://bugs.launchpad.net/bugs/150797 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
Since my last update, the problem returned, except that the background color I set in .bashrc is not ignored. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 112839] Re: I/O error on access to SMB shares of OS/2 Warp 4 host mounted in Ubuntu 7.04
I confirm validity of TEN's comment 8 using 2.6.24-12-generic and 3.0.28a. -- I/O error on access to SMB shares of OS/2 Warp 4 host mounted in Ubuntu 7.04 https://bugs.launchpad.net/bugs/112839 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
Ben Collins wrote It's way to [sic] unstable, That's utter nonsense. In all the years I've been using Linux since sometime last century, my kernel lines have not had vga= parameters only briefly when necessary to overcome brokenness such as this. With the exception of this bug, such periods without have always been very brief, days or at most two weeks. Six months of a choice between being stuck with the exclusively Ubuntu only 80x25 possible on the ttys, or using any of the many major distros not suffering this ridiculous bug instead is inexcusable. Fedora 8 doesn't have this. Etch doesn't have this. SUSE 10.3 doesn't have this. Mandriva 2008 doesn't have this. Knoppix doesn't have this. OTOH, every release of Ubuntu since my first exposure to it over 3 years ago has given me consoles that are different from what just works elsewhere. Whatever it is that Ubuntu does differently with framebuffer from what other distros do is simply broken, and should be changed to conform to what seems to be bulletproof everywhere else. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 32123] Re: initramfs not generated correctly on upgrade to Dapper
Summary should be changed from initramfs not generated correctly on upgrade to Dapper to initramfs not generated correctly on dist- upgrade. This just happened to me going from Gutsy to Hardy. Marking kernels for reinstallation and applying in Synaptic made system bootable with Hardy kernels and newer larger initrds. -- initramfs not generated correctly on upgrade to Dapper https://bugs.launchpad.net/bugs/32123 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
I upgraded from Gutsy to Hardy and observed no improvement. Then I added vesafb to /etc/modules. This proved a partial solution. I no longer need to manually modprobe vesafb, but there's a much too long 25 second delay between Grub menu selection and observing anything but black on the screen again. The boot process is far along before any startup messages can be observed. mga gfxcard. 1.13 GHz CPU. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
Upgrading to the latest kernel didn't help my mga system at all. My /etc/modprobe.d/blacklist-framebuffer file has no content. No matter what combination of modules I do or don't include in /etc/initramfs- tools/modules before doing 'update-initramfs -u -k all', I get entirely black screen between Grub menu and KDM login screen, and unless I first 'modprobe vesafb', also on reboot after X closes, until POST begins. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
FWIW, this bug does not apply to OpenSUSE 10.3, Mandriva 2008, or Feisty, and I highly doubt it applies to Fedora 8 or any other recent distro. Apparently the devs think those who rightly expect their fb consoles to work correctly should use something other than Gutsy or Hardy, or write their own script to load the necessary module(s), or install some gfxcard other than Intel. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
As Massimo Dal Zotto wrote, the original problem (black screen on tty[1-6]) is not related to nvidia or other hardware. The problem exists for non-NVidia users as well, such as mga and intel. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
I've followed recommendations exactly, and variations thereof, with both Matrox and Intel chips. In no case has lsmod ever shown vesafb as having been loaded by the time init completes. Only when I modprobe vesafb manually do I get working framebuffer consoles. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
depmod -a didn't change anything for me. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
I just did updates again, and tried as NeverMind suggested in comment 89. As I have Intel 845GL, I did s/nvidiafb/intelfb/. With the default stanza and vga=788 I still have useless ttys, although there is some scrambled junk on the top few rows of each instead of entirely black. This system also has Mandriva 2008 installed. Console framefuffer video works nicely as expected using it. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
I tried on another machine with 2.6.22-14-, both 386 generic, and Matrox G400. More less the same problem, except that once KDM starts, trying to switch to tty[1-6] gives me the KDM background image instead of a black screen, but all during init it's all black. vesafb does not show up in lsmod output. fbcon and matrox_w1 do. When I do modprobe vesafb manually in Konsole, I get the ttys video working. Alternatively, I can switch to a tty, login blindly, and modprobe vesafb there for the same result. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 151490] Re: Bootup splash screen causes problems
*** This bug is a duplicate of bug 129910 *** https://bugs.launchpad.net/bugs/129910 ** This bug has been marked a duplicate of bug 129910 tty[1-6] are active but display nothing in Gutsy -- Bootup splash screen causes problems https://bugs.launchpad.net/bugs/151490 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 150638] Re: framebuffer mode results in black screen starting with kernel 2.6.22-13-generic
Using what hardware? With 2.6.22-14 on my Intel 845G, vga= framebuffer modes blank the console screens, but video=vesafb has no apparent effect. -- framebuffer mode results in black screen starting with kernel 2.6.22-13-generic https://bugs.launchpad.net/bugs/150638 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 147606] Re: Intelfb completely b0rken
Same problem on 845G. 80x25 is horrible. Please fix this ASAP. -- Intelfb completely b0rken https://bugs.launchpad.net/bugs/147606 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 150638] Re: framebuffer mode results in black screen starting with kernel 2.6.22-13-generic
Looks like another bug 129910 duplicate. -- framebuffer mode results in black screen starting with kernel 2.6.22-13-generic https://bugs.launchpad.net/bugs/150638 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
I tried what MOM2007 recommended without success, and with my i845G with removed usplash wound up with: /etc/initramfs-tools/modules: fbcon intelfb vesafb /etc/modprobe.d/blacklist-framebuffer ... # blacklist i810fb # blacklist intelfb # blacklist vesafb # blacklist vga16fb No success, but I see in /lib/modules/2.6.22-14-generic/kernel/drivers/video/console only fbcon, no intelfb, no i810fb no vga16fb, (but ../intelfb/intelfb.ko does exist - why there?) even though in /boot/config-23.6.22-14-generic: ... CONFIG_FB=y CONFIG_FB_VESA=m CONFIG_FB_VGA16=m CONFIG_FRAMEBUFFER_CONSOLE=m CONFIG_FB_I810=m CONFIG_FB_INTEL=m... As expected after not finding those .ko files, lsmod finds neither vesafb nor i810fb, nor vga16fb, but only fbcon, and not even intelfb. Why didn't intelfb load? Why are there no .ko files for the rest? I tried reducing /etc/initramfs-tools/modules to only intelfb, also without success. Even after update-initramfs -u that way intelfb fails to load on boot, and modprobe intelfb produces no apparent effect. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 150797] Re: Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
I've since determined that with 845G a BIOS upgrade may provide support for standard framebuffer vga= modes. -- Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120 https://bugs.launchpad.net/bugs/150797 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 150797] Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
Public bug reported: Binary package hint: usplash I installed from kubuntu-7.10-beta-alternate this AM, then immediately upgraded to whatever state is on the mirrors. On all Intel video chips that I've used (i810, i815, 845G), none of the common framebuffer vga= modes (785, 788, 791, 0x31a, etc.) work. The only functional mode I've found other than normal 80x25 is 0x120, which is 25 row by 132 column. Setting splash=0 and vga=0x120 on the kernel lines in menu.lst causes bootup video to initialize correctly, but after usplash finishes and I return to any of the consoles from X, the characters on screen have been reset to the 80x25 size, but are laid out as if there were still 25 rows of 132 columns, with chars 80 spilling onto subsequent rows, and new rows appended where previous rows end. As a result, the consoles are unusable. The last rows and columns seem to be off the bottom of the screen. The only fixes I have found are suffering to keep 80x25, or apt-get remove usplash. I did the latter before booting after the upgrade, so don't know if a newer version than 0.5-5 might have behaved differently. Upstream kernel bug http://bugzilla.kernel.org/show_bug.cgi?id=7513 might be related. ** Affects: usplash (Ubuntu) Importance: Undecided Status: New -- Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120 https://bugs.launchpad.net/bugs/150797 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 134983] Re: Cannot mount /home on /dev/hda16
Mandriva 2008 and OpenSUSE have workarounds to use legacy drivers instead of libata to access all existing partitions. Have you found a workaround that works in Gutsy? I'm having no luck. :-( -- Cannot mount /home on /dev/hda16 https://bugs.launchpad.net/bugs/134983 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
