[Ubuntu-x-swat] [Bug 1407303] [NEW] Made in automatic
Public bug reported: using xdiagnose ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 3 18:49:04 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobility Radeon HD 4570 [1025:0206] InstallationDate: Installed on 2014-12-03 (31 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Acer Aspire 5536 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=96a6eb01-1b67-4520-b2ba-236dbbe63818 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV50PU dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd10/22/2009:svnAcer:pnAspire5536:pvr0100:rvnAcer:rnJV50PU:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5536 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Jan 3 18:46:41 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu 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/1407303 Title: Made in automatic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1407303/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
I'm seeing this very same bug on a fresh install on a Asus A53J, quite similar hardware (Elantech, NVIDIA Corporation GF119M [GeForce GT 520M] (rev a1)) Any possibility to have it solved without loosing features? It is very annoying see the touchpad freeze every few minutes. Removing the option to deactivate while typing reduces the freeze frequency, but I NEED the two finger scrolling for productivity, and this one makes it freeze less often, but still enough... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1061556] Re: compiz crashed with SIGABRT in assertion failure !xcb_xlib_unknown_seq_number from append_pending_request() [xcb_io.c:158] ... from XInitExtension() from XextAddDis
That version has reached EOL since a while, so it will not receive update. If that issue still exist, report again using ubuntu-bug. ** Changed in: libx11 (Ubuntu) Status: Confirmed = Invalid ** Changed in: compiz (Ubuntu) Status: Confirmed = Invalid ** Changed in: compiz Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1061556 Title: compiz crashed with SIGABRT in assertion failure !xcb_xlib_unknown_seq_number from append_pending_request() [xcb_io.c:158] ... from XInitExtension() from XextAddDisplay() from ?? To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1061556/+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 1047136] Re: compiz crashed with SIGSEGV in intelDestroyContext() from intelCreateContext() from dri2CreateContextAttribs() from dri2CreateNewContextForAPI() from dri2CreateNewCon
That version has reached EOL since a while, so it will not receive update. If that issue still exist, report again using ubuntu-bug. ** Changed in: mesa (Ubuntu) Status: Confirmed = Invalid ** Changed in: compiz (Ubuntu) Status: Confirmed = Invalid ** Changed in: compiz Status: Confirmed = Invalid ** Changed in: mesa Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1047136 Title: compiz crashed with SIGSEGV in intelDestroyContext() from intelCreateContext() from dri2CreateContextAttribs() from dri2CreateNewContextForAPI() from dri2CreateNewContext() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1047136/+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 1365695] Re: No longer able to use GUI after update
The issue I described in post #39 is still present (I'm stuck to ubuntu-drivers-common to version 1:0.2.91.4), but seems what I described is a different bug than many users reported here. What I need to do? Open a new bug? Thanks -- 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/1365695 Title: No longer able to use GUI after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1037732] Re: compiz crashed with SIGSEGV in xcb_glx_gen_textures_data_length() from glGenTextures() from PrivateTexture::PrivateTexture() from GLTexture::GLTexture() from TfpTextu
That version has reached EOL since a while, so it will not receive update. If that issue still exist, report again using ubuntu-bug. ** Changed in: mesa (Ubuntu) Status: New = Invalid ** Changed in: compiz (Ubuntu) Status: New = Invalid ** Changed in: compiz Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1037732 Title: compiz crashed with SIGSEGV in xcb_glx_gen_textures_data_length() from glGenTextures() from PrivateTexture::PrivateTexture() from GLTexture::GLTexture() from TfpTexture::TfpTexture() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037732/+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 531208]
+1 thank you Ruslan. I'm guessing that at this point we should be asking for this to be implemented on Wayland, as it seems that X will be deprecated soon enough and its input code is complex and strange enough (no screensaver when a pop-up menu is open, for instance) that this won't make it. -- 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/531208 Title: Need way to insert arbitrary unicode characters in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/531208/+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 758609] Re: natty beta Ubuntu Classic (No effects) SDL|openGL window always on top
EOL have been reached, so no more maintenance. If that issue still exist, then report again using ubuntu-bug. ** Changed in: metacity (Ubuntu) Status: Confirmed = Invalid ** Changed in: fglrx-installer (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/758609 Title: natty beta Ubuntu Classic (No effects) SDL|openGL window always on top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/758609/+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 531208]
Thank you Ruslan. I do stress to the developers that this is a workaround, not a solution, due to issues such as the user of sticky keys. -- 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/531208 Title: Need way to insert arbitrary unicode characters in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/531208/+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 531208]
+ 10 for the implementation of this UNICODE-FEATURE. At the moment I'm coding on a Keyboard-Firmware (ErgoDox). Problem is that I can send UNICODE-Chars easy and nice with the GNOME-Method : CTRL+Shift+digits, but there is no way to send them to QT-Based Programms. So keep calm and implement the Shortcut which is still implemented in Gnome (and please, please, please don't choose another one like CTRL+ META or such different Stuff...) Keep things easy and implement like it still works in Gnome. BTW: Thanks a lot for all your work. I love KDE. -- 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/531208 Title: Need way to insert arbitrary unicode characters in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/531208/+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 1181651] Re: ldconfig problem with 64-bit nvidia driver packages
Had a problem with this bug. Found a fix here, http://steamcommunity.com/app/221410/discussions/5/828939163894026239/?l=german -- 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/1181651 Title: ldconfig problem with 64-bit nvidia driver packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1181651/+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 1407362] [NEW] fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build
Public bug reported: Tried to install on ASUS K70AB with ATI Radeon HD 4570 discrete graphics card. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSBuildLog: DKMS make.log for fglrx-8.970 for kernel 3.16.0-28-generic (i686) Sat Jan 3 17:36:03 CST 2015 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.16.0-28-generic/build/include not found or incomplete file: /lib/modules/3.16.0-28-generic/build/include/linux/version.h DKMSKernelVersion: 3.16.0-28-generic Date: Sat Jan 3 17:36:07 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobility Radeon HD 4570 [1043:1b32] InstallationDate: Installed on 2015-01-03 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release i386 (20141022.1) MachineType: ASUSTeK Computer Inc. K70AB PackageVersion: 2:8.970-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K70AB dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr210:bd09/17/2009:svnASUSTeKComputerInc.:pnK70AB:pvr1.0:rvnASUSTeKComputerInc.:rnK70AB:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K70AB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Jan 3 17:43:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0LVDS VGA-0 xserver.version: 2:1.16.0-1ubuntu1.2 xserver.video_driver: radeon ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 ubuntu utopic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1407362 Title: fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1407362/+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
