[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta
It may be related to the "Multi Monitors Add-On" extension. I've disabled it and now it works fine. Will update if I have any more crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722353 Title: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta
I have the same issue, running on a laptop with a dual monitor splitter plugged in my displayPort. The crash happens under Wayland and XOrg. I've disabled auto-source selection on the monitors. The crash happens only when I log-in after the session has been locked. It also happens when I press the reset switch on my displayPort splitter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722353 Title: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta
Disabling Power Saving on the monitors seems to help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722353 Title: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802217] [NEW] simple-scan select Gray instead of Lineart for text scans (Fujitsu S300)
Public bug reported: When I scan a page in text mode, simple-scan selects Gray mode instead of Lineart. This result in a less than satisfactory scan result. With XSane, I can scan using Lineart mode without issue. I use a Fujitsu ScanSnap S300 duplex scanner. It would be really nice to have an option or a config file to force the scan mode for a scan type (Color/Text). ** Affects: simple-scan (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/802217 Title: simple-scan select Gray instead of Lineart for text scans (Fujitsu S300) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/802217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802217] Re: simple-scan select Gray instead of Lineart for text scans (Fujitsu S300)
** Attachment added: simple-scan -d output https://bugs.launchpad.net/bugs/802217/+attachment/2181957/+files/simple-scan.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802217 Title: simple-scan select Gray instead of Lineart for text scans (Fujitsu S300) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/802217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623438] Re: Font size not correct in merged sandvich PDF
I'm having similar issue. I can confirm that it is not related to Cuneiform. I'm using ocropus (ocroscript recognize) (which uses Tesseract) and I have check the resulting .html (hocr) which seems valid and pixel perfect. However, hocr2pdf misalign the text with their related bounding boxes. I've tried ocroscript recognize with and without the --charboxes options and the result is always wrong (the text has an offset on the Y axis). This is with exactimage 0.8.1-3build1 on Ubuntu Natty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/623438 Title: Font size not correct in merged sandvich PDF To manage notifications about this bug go to: https://bugs.launchpad.net/cuneiform-linux/+bug/623438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645632] [NEW] [arrandale] GPU lockup 9b0aacb1
Public bug reported: Binary package hint: xserver-xorg-video-intel When I'm connected to an external monitor (KVM Switch) and the lid of the laptop is closed. All output is directed to the external monitor. When I open the lid of the lapop, I get black screen on both the laptop monitor. There is no way to unfreeze the computer other than a force shutdown by pressing the power button. lsb_release -rd Description:Ubuntu maverick (development branch) Release:10.10 ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Chipset: arrandale DRM.card0.DisplayPort.1: 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///wAw5FECAAATAQOAHxF4CmsVl1lWjCgeUFQBAQEBAQEBAQEBAQEBAQEBEhtWeFAADjAgIDUANq4QAAAZ/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFdIMS1UTEMzAOw= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Wed Sep 22 15:59:46 2010 DkmsStatus: vboxdrv, 3.2.8, 2.6.35-22-generic, x86_64: installed vboxnetadp, 3.2.8, 2.6.35-22-generic, x86_64: installed vboxnetflt, 3.2.8, 2.6.35-22-generic, x86_64: installed DumpSignature: 9b0aacb1 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100907) InterpreterPath: /usr/bin/python2.6 MachineType: Hewlett-Packard HP G42 Notebook PC ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=aa86e7ef-dd96-4184-84e9-fe9098ead379 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: SourcePackage: xserver-xorg-video-intel Title: [arrandale] GPU lockup 9b0aacb1 UserGroups: dmi.bios.date: 02/10/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1425 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd02/10/2010:svnHewlett-Packard:pnHPG42NotebookPC:pvr049D102027102:rvnHewlett-Packard:rn1425:rvr54.13:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 049D102027102 dmi.sys.vendor: Hewlett-Packard system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-22-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash freeze maverick -- [arrandale] GPU lockup 9b0aacb1 https://bugs.launchpad.net/bugs/645632 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 645632] Re: [arrandale] GPU lockup 9b0aacb1
** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624851/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624852/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624853/+files/Dependencies.txt ** Attachment added: IntelGpuDump.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624854/+files/IntelGpuDump.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624855/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624856/+files/Lsusb.txt ** Attachment added: PciDisplay.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624857/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624858/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624859/+files/ProcInterrupts.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624860/+files/ProcMaps.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624861/+files/ProcModules.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624862/+files/ProcStatus.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624863/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624864/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624865/+files/UdevLog.txt ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624866/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624867/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624868/+files/Xrandr.txt ** Attachment added: glxinfo.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624869/+files/glxinfo.txt ** Attachment added: i915_error_state.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624870/+files/i915_error_state.txt ** Attachment added: peripherals.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624871/+files/peripherals.txt ** Attachment added: setxkbmap.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624872/+files/setxkbmap.txt ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624873/+files/xdpyinfo.txt ** Attachment added: xkbcomp.txt https://bugs.launchpad.net/bugs/645632/+attachment/1624874/+files/xkbcomp.txt -- [arrandale] GPU lockup 9b0aacb1 https://bugs.launchpad.net/bugs/645632 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 389040] Re: Realtek ALC272 not working in 9.04 but its working under 8.10
I Have the same issue, I found one someone else blog (http://tjmcgrew.blogspot.com/2009/07/toshiba-nb205-part-2.html) that adding the following line to /etc/modprobe.d/alsa-base.conf give sound thru the headphones jack (nothing from the speaker) : options snd-hda-intel model=asus-mode4 Maybe this can help fix this issue. -- Realtek ALC272 not working in 9.04 but its working under 8.10 https://bugs.launchpad.net/bugs/389040 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
