[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
Re #74 (Roland Meier): the message in #37 is "Could no open output pipe", which is somewhat different from the "broken pipe" message. Interestingly, I've also seen the broken pipe message in an older 13.10 system, which brought up the graphical interface but froze after a while. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
The keepers of the archive need to do something about this bug to reflect the fact that it is not Nvidia-specific. Several people have reported encountering it with Intel hardware. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
I just "upgraded" a system from Kubuntu 14.04 to Kubuntu 14.10, and the "broken pipe" error popped up. Some questions for the suffering populace: 1. Does the error occur with 14.04 or only with 14.10? 2. Does it occur with 14.10 installed directly or only with 14.10 upgraded from 14.04? In my experience it is specifically associated with upgrading 14.04 to 14.10 but is not associated with specific video hardware since it has been reported both for Nvidia video and Intel video. Does anyone have experience to the contrary? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1412594] [NEW] System hangs when kstart used in autostart script
Public bug reported: I was trying to use kstart to start three programs in three different desktops after login, like this: kstart --desktop 1 firefox kstart --desktop 2 kmail kstart --desktop 3 konsole After (apparently) executing the script, the system hung solidly. I tried this more elaborate version of the same thing: #! /bin/sh kstart --desktop 1 firefox & kstart --desktop 2 kmail & kstart --desktop 3 konsole & exit but the behavior was the same. I'm running Kubuntu 14.10 with release 4:4.14.2-0ubuntu1~ubuntu14.10~ppa1 of kde-runtime. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 19 18:12:06 2015 InstallationDate: Installed on 2015-01-10 (9 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts kubuntu third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1412594 Title: System hangs when kstart used in autostart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1412594/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
I.ve installed the 20140923 microcode update. It solved the buffer underrun problem I was having but not the broken pipe problem. The reason I thought it would help is that I saw a post somewhere saying that this update worked but the previous one (20140624) did not. I've been trying without success to find that post again to see just what it was that this update was supposed to have fixed. With this update I get the line in dmesg that says CPU0 microcode updated early to revision 0x29, date = 2013-06-12 The form of the line seems correct but the date looks suspicious. Meanwhile thes primary problem remains unsolved -- I can't get past the "broken pipe" message. After it comes up I get bounced to a virtual console. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
After poking around I learned that the cure is to install a correction to the Intel microcode. That in turn requires installing the"intel- microcode 2.20140913.1ubuntu2 source package, which is available from Launchpad. However, I haven't yet figured out how to actually do that. The Archlinux folks have some information on this subject. I didn't realize that Linux actually has the ability to install mods to the Intel microcode. If any one else decides to follow through on this, please post your findings here. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
i just installed the 3.18 kernel and still get the broken pipe. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
This bug report is mistitled since the same bug appears on machines (like mine) with Intel integrated graphics. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
I too get this message in Kubuntu 14.10. I have a Lenovo laptop with Intel integrated graphics. I actually have two Kubuntu 14.10's in different partitions on this machine. I'm writing this from what I'll call P1, which I had abandoned because the partition was too small for my needs. So I created P2, which has plenty of space. P2 was running just fine for a couple of months when it suddenly started misbehaving badly. After a reboot (to P2) I got just a black screen, though I was able to get to a virtual console with Ctl-Alt-F1 and thus get much more information about the system. When I booted P2 via a slightly different route I got the "error while reading from descriptor" message. So I now have P1, which works but is not fully usable, and P2, which gives me a black screen. That opens up some potential ways of diagnosing the problem since I can compare the two systems. In particular, I ran dmsg in both systems and compared the two outputs to find the first significant difference. I found this sequence in P2: [1.143424] [drm] Replacing VGA console driver [1.143428] checking generic (e000 41) vs hw (e000 1000) [1.143429] fb: switching to inteldrmfb from VESA VGA [1.143449] Console: switching to colour dummy device 80x25 But in P1 (the correct one) the lines 428 and 429 are absent. This probably points directly to the bug if only I knew how to interpret it. P2 was fully updated when it started misbehaving; P1 was not. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1081185] Re: Touchpad can't be deactivated after a while
I doubt if this will be of much help: pa@morchella:~$ apport-collect 1081185 Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated. ERROR: connecting to Launchpad failed: [Errno 2] No such file or directory You can reset the credentials by removing the file "/home/pa/.cache/apport/launchpad.credentials" pa@morchella:~$ ls .cache/apport pa@morchella:~$ It seems that I can circumvent this bug most of the time by using the Synaptic program to deactivate the touchpad when the mouse is active (something that I would have expected to be in System Settings, but it isn't). But this might be interesting: [36.852] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8) [36.852] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall" [36.853] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall" [36.853] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons" [36.853] (II) LoadModule: "synaptics" [36.853] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so [37.013] (II) Module synaptics: vendor="X.Org Foundation" [37.013]compiled for 1.12.99.905, module version = 1.6.2 [37.013]Module class: X.Org XInput Driver [37.013]ABI class: X.Org XInput driver, version 18.0 [37.013] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad' [37.013] (**) SynPS/2 Synaptics TouchPad: always reports core events [37.013] (**) Option "Device" "/dev/input/event8" [37.013] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5664 [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4682 [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255 [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15 [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7 [37.013] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0" [37.013] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found [37.013] (**) SynPS/2 Synaptics TouchPad: always reports core events [37.013] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input8/event8" [37.013] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13) [37.013] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5 [37.013] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75 [37.013] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.038 [37.013] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1 [37.013] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1 [37.013] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000 [37.013] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4 [37.014] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found [37.014] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1) [37.014] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates" [37.014] (II) config/udev: Adding input device Ideapad extra buttons (/dev/input/event7) [37.014] (**) Ideapad extra buttons: Applying InputClass "evdev keyboard catchall" [37.014] (II) Using input driver 'evdev' for 'Ideapad extra buttons' [37.014] (**) Ideapad extra buttons: always reports core events [37.014] (**) evdev: Ideapad extra buttons: Device: "/dev/input/event7" [37.014] (--) evdev: Ideapad extra buttons: Vendor 0 Product 0 [37.014] (--) evdev: Ideapad extra buttons: Found keys [37.014] (II) evdev: Ideapad extra buttons: Configuring as keyboard [37.014] (**) Option "config_info" "udev:/sys/devices/platform/ideapad/input/input7/event7" [37.014] (II) XINPUT: Adding extended input device "Ideapad extra buttons" (type: KEYBOARD, id 14) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1081185 Title: Touchpad can't be deactivated after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1081185/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1081185] [NEW] Touchpad can't be deactivated after a while
Public bug reported: I'm running Kubuntu 12.04.1. When I first start a session, I can (and do) deactivate the touchpad with Fn-F6 on my Lenovo laptop. But later on, something -- I don't know what -- reactivates the touchpad and I can't shut it off using normal means. At the same time the Systems Settings section for the touchpad changes and no longer offers the option of shutting off the touchpad if the mouse is active. Fortunately I seem to be able (so far) to deactivate the touchpad with this: xinput set-prop 13 "Device Enabled" 0 but that shouldn't be necessary. I have version 1.6.2-1ubuntu1~precise2 of server-xorg-input-synaptics. But I'm not sure that's the program responsible for the problem. ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Package changed: update-manager-core (Ubuntu) => xserver-xorg-input- synaptics (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1081185 Title: Touchpad can't be deactivated after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1081185/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 703602] Re: Brightness controls not working
I still have this bug. I'll test it in Natty once I have Natty installed. But as of this very moment the upgrade isn't available. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/703602 Title: Brightness controls not working ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 703602] Re: Brightness controls not working
I still have this bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/703602 Title: Brightness controls not working ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 710144] Re: Xsession: unable to launch "" X session --- "" not found; falling back to default session.
And so did I. (also an akonadi error, FWIW). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/710144 Title: Xsession: unable to launch "" X session --- "" not found; falling back to default session. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 540112] Re: Can not change LCD brightness on Lenovo Y450 laptop
What is the best way to install the EnableBrightnessControl fix if xorg.conf doesn't exist (a common situation now)? I tried creating xorg.conf as Section "Device" Identifier "Configured Video Device" Driver "fbdev" Option "RegistryDwords" "EnableBrightnessControl=1" EndSection with material copied from xorg.conf.failsafe but that didn't have any effect. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/540112 Title: Can not change LCD brightness on Lenovo Y450 laptop ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 703602] Re: Brightness controls not working
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/703602 Title: Brightness controls not working ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 703602] [NEW] Brightness controls not working
Public bug reported: Binary package hint: xorg I first noticed that my screen was too bright and tried to adjust the brightness with Fn-F5. Nothing happened right away, but after that something that looked like a brightness control bar would pop up on my screen every minute or so and then disappear. There was no way I could get at it. I also tried using the brightness control in Power Management, but it did nothing at all. The tail of xorg.0.log looks like this (it doesn't seem at all helpful): -hsync -vsync (47.4 kHz) [ 487.030] (II) intel(0): EDID vendor "SEC", prod id 21069 [ 487.030] (II) intel(0): Printing DDC gathered Modelines: [ 487.030] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz) And here's the hardware info: pwa@Asus-laptop:/var/log$ hwinfo --gfxcard 08: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_8086_2a42 Unique ID: _Znp.+Z2cv4pDpdF SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2a42 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1862 Revision: 0x09 Driver: "i915" Driver Modules: "drm" Memory Range: 0xfe40-0xfe7f (rw,non-prefetchable) Memory Range: 0xd000-0xdfff (ro,non-prefetchable) I/O Ports: 0xdc00-0xdc07 (rw) IRQ: 44 (42722 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v8086d2A42sv1043sd1862bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 09: PCI 02.1: 0380 Display controller [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_8086_2a43 Unique ID: ruGf.W0QEpw5u4F5 SysFS ID: /devices/pci:00/:00:02.1 SysFS BusID: :00:02.1 Hardware Class: graphics card Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1862 Revision: 0x09 Memory Range: 0xfe80-0xfe8f (rw,non-prefetchable) Module Alias: "pci:v8086d2A43sv1043sd1862bc03sc80i00" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #8 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-25.43-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 DRM.card0.DisplayPort.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.DisplayPort.2: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.HDMI_Type_A.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1366x768 edid-base64: AP///wBMo01SAAATAQOAIxR4CsClnldXlyYUUFQBAQEBAQEBAQEBAQEBAQEBQRxWoFAAFjAwICUAYcYQAAAZDwAAAB60AnQA/gBTQU1TVU5HCiAgICAg/gAxNjBBVDA2LUEwMQogAJ4= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Sun Jan 16 11:16:51 2011 DkmsStatus: alsa-hda-realtek-ignore-sku, 1.0.23.diwic, 2.6.35-23-generic, x86_64: installed alsa-hda-realtek-ignore-sku, 1.0.23.diwic, 2.6.35-25-generic, x86_64: installed alsa-hda-realtek-ignore-sku, 1.0.23.diwic, 2.6.35-24-generic, x86_64: installed vboxhost, 3.2.12, 2.6.35-25-generic, x86_64: installed vboxhost, 3.2.12, 2.6.35-24-generic, x86_64: installed GdmLog: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: ASUSTeK Computer Inc. K60IJ ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=bdf6b84b-d3dd-47d5-aa7b-af3309e08dc3 ro quiet splash ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 12/03/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K60IJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.
[Ubuntu-x-swat] [Bug 630320] Re: 1280x1024 resolution lost after reboot
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543505/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543506/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543507/+files/Dependencies.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543508/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543509/+files/Lsusb.txt ** Attachment added: "PciDisplay.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543510/+files/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543511/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543512/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543513/+files/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543514/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543515/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543516/+files/UdevLog.txt ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543517/+files/XorgLog.txt ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543518/+files/XorgLogOld.txt ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543519/+files/Xrandr.txt ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543520/+files/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543521/+files/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/630320/+attachment/1543522/+files/xkbcomp.txt -- 1280x1024 resolution lost after reboot https://bugs.launchpad.net/bugs/630320 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 630320] [NEW] 1280x1024 resolution lost after reboot
Public bug reported: Binary package hint: xorg Before upgrading to kernel level 2.6.32-24, I was unable to get screen resolution better than 1024x768. After the upgrade I can get what I want via System Settings / Display: 1280 x 1024. But the resolution setting is lost after a reboot; after the reboot the resolution is again 1024x768. The correct setting is preserved over logout, however. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Sat Sep 4 12:36:38 2010 DkmsStatus: Error: [Errno 2] No such file or directory GdmLog: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/pwa/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon cat: /var/log/gdm/:0.log: No such file or directory GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=b024207c-442d-49c3-ab43-ae2135cd3ca8 ro modeset=0 quiet splash ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg XorgConf: Section "Monitor" Identifier "VGA-1" # 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz Modeline "1280x1024" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync EndSection dmi.bios.date: 10/16/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd10/16/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMSE2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-24-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- 1280x1024 resolution lost after reboot https://bugs.launchpad.net/bugs/630320 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 159007] Re: Screen and Graphics lose resolution configuration after reboot
This problem has resurfaced in 10.04 Lucid. Until the 2.6.32-24 kernel release I was unable to get resolutions greater than 1024x768. This later kernel release solved that problem -- but now I still get sent back to the lower resolution after a reboot. -- Screen and Graphics lose resolution configuration after reboot https://bugs.launchpad.net/bugs/159007 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
