[Bug 1307105] Re: Kernel install fails due PAE checks
I also ran into this problem with Xubuntu 16.04 LTS. I'm running an Intel Pentium M 735, Dothan, (2MB L2 Cache, 1.70 GHz, 400 MHz FSB) (CPUID: 6.D.6 (hex) or 06D6h or 6.13.6 (dec)). When I lookup the specification on the Intel site, then it says: Physical Address Extensions (PAE) 32-bit is available. (source: http://ark.intel.com/products/27588/Intel-Pentium-M-Processor-735-2M-Cache-1_70A-GHz-400-MHz-FSB#@specifications ) Are there any adverse effects known about the boot parameter "forcepae"? What I need to know is if the compiled stock kernel / compiler implemented work-arounds for the W25 and W40 errata* to the Dothan (stepping B1) family of processors. If that is so, then the PAE flag can be set / forced without problems. * Intel Celeron M Specification Update errata W25: Upper Four PAT Entries Not Usable with Mode B or Mode C Paging W40: INIT Does Not Clear Global Entries in the TLB Problem: INIT may not flush a TLB entry when: 1. The processor is in protected mode with paging enabled and the page global enable flag is set (PGEbit of CR4 register) 2. G bit for the page table entry is set 3. TLB entry is present in TLB when INIT occurs Implication: Software may encounter unexpected page fault or incorrect address translation due to a TLB entry erroneously left in TLB after INIT. Workaround: Write to CR3, CR4 (settingbits PSE, PGE or PAE) or CR0 (setting bits PG or PE) registers before writing to memory early in BIOS code to clear all the global entries from TLB. (source: http://download.intel.com/support/processors/mobile/celeron/sb/30030336.pdf ) See also: http://ubuntuforums.org/showthread.php?t=2326769=13499191#post13499191 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307105 Title: Kernel install fails due PAE checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990887] Re: LightDM does not suspend when lid is closed
My system is using the following greeter: /usr/sbin/lightdm-gtk-greeter I'm running: Distributor ID: Ubuntu Description: Ubuntu 12.04.5 LTS Release: 12.04 Codename: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990887 Title: LightDM does not suspend when lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/990887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990887] Re: LightDM does not suspend when lid is closed
I experience the same problem. When someone closes my laptop lid, when no-one is logged in, the laptop keeps running and gets seriously hot like a toaster oven. It is bound to fry one day. Please increase the priority of this issue. I'm running: Distributor ID: Ubuntu Description:Ubuntu 12.04.5 LTS Release:12.04 Codename: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990887 Title: LightDM does not suspend when lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/990887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664627] Re: auto-hide broken on unmounting of external device
In which version will the fix be released? (or how can I determine that myself?) I'm experiencing this bug and am currently on xfce4-panel version 4.8.6 and xfce4-places-plugin version 1.2.0-3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/664627 Title: auto-hide broken on unmounting of external device To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-places-plugin/+bug/664627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548631] Re: xubuntu keyboard layout switch shortcuts are not remembered
This bug affects me since a relatively short wile too. Was there a regression? My default keyboard layout settings are lost after a re-login. I'm on XUbuntu 12.04.5 LTS running on a 32 bit Intel platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/548631 Title: xubuntu keyboard layout switch shortcuts are not remembered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-xkb-plugin/+bug/548631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548631] Re: xubuntu keyboard layout switch shortcuts are not remembered
Additional information: When I try Marzata's workaround stated above, xfce4-xkb-plugin crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/548631 Title: xubuntu keyboard layout switch shortcuts are not remembered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-xkb-plugin/+bug/548631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015211] Re: Ubiquity installed grub-efi when it should have installed grub-pc
Steve Langasek (vorlon) wrote on 2013-01-15: The current on-disk layout tells you even *less* about how the disk will be booted than the current boot method for the removable media tells you. Dear Steve, if the goal is: Create a dual boot system on top of a pre installed Win7x64. Why would the on-disk layout not tell you anything about how Win7x64 is currently installed an how it can be booted? The system gets its operating system from the disk and obviously contains the only source of the bootable Win7x64 software. You should not make any assumptions about which boot sequence will be used to boot the disk, because that is the real unknown here. (Assumptions are the mother of all f*ck-ups. :) If you don't know and can't find out, just let the user decide / overwrite. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015211] Re: Ubiquity installed grub-efi when it should have installed grub-pc
Conclusion When the Live CD is booted with an UEFI boot sequence, Grub erroneously expects a GPT structured HD, even if the boot HD is msdos/MBR structured. Grub doesn't installs itself to the MBR. When the same Live CD is booted with a non UEFI boot sequence Grub is automatically installed correctly in the MBR and Win7 is added too. Discussion Because more and more computers support UEFI nowadays, the out of the box installation of Grub and hence Ubuntu from the Live CD is expected to fail more often. I would suggest that the installation process should be updated to alert the user of a UEFI boot sequence conflicting with a non GPT structured target installation HD or better yet, if possible automatically make the correct Grub installation selection accordingly to the installation target HD's structure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015211] Re: Ubiquity installed grub-efi when it should have installed grub-pc
The installation CD was booted in a UEFI sequence (default behavior). In my opinion the boot sequence for the installation CD should not lead to assumptions about the format of the system HD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015211] Re: Ubiquity installed grub-efi when it should have installed grub-pc
I verified in the intial install logs (/var/install/syslog) that erroneously grub-efi was installed instead of grub-pc: Code: Jun 13 13:45:35 ubuntu grub-installer: info: architecture: amd64/efi ... Jun 13 13:45:38 ubuntu grub-installer: Removing grub-pc ... Jun 13 13:45:39 ubuntu grub-installer: Purging configuration files for grub-pc ... Jun 13 13:45:40 ubuntu grub-installer: Removing grub-gfxpayload-lists ... Jun 13 13:45:40 ubuntu grub-installer: Removing grub-pc-bin ... ... Jun 13 13:45:44 ubuntu ubiquity: The following extra packages will be installed: Jun 13 13:45:44 ubuntu ubiquity: efibootmgr grub-common grub-efi-amd64 grub-efi-amd64-bin grub2-common ... Jun 13 13:45:57 ubuntu ubiquity: Setting up grub-efi (1.99-21ubuntu3.1) ... ... Jun 13 13:45:58 ubuntu grub-installer: info: Installing grub on 'dummy' Jun 13 13:45:58 ubuntu grub-installer: info: grub-install supports --no-floppy Jun 13 13:45:58 ubuntu grub-installer: info: Running chroot /target grub-install --no-floppy --force Jun 13 13:45:59 ubuntu grub-installer: Installation finished. No error reported. Jun 13 13:45:59 ubuntu grub-installer: info: grub-install ran successfully -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250517] Re: gvfs performs slowly on bulk sftp transfers
I also ran into the same problem on LUbuntu 10.04, which increases big file transfers times with hours. Could it be that sftp from Nautilus selects a different cipher for its encryption? Presumably des (the default protocol 1 cipher), judging from the speed drop compared to plain sftp? For full details see this posting: http://ubuntuforums.org/showthread.php?p=12275118#post12275118 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/250517 Title: gvfs performs slowly on bulk sftp transfers To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/250517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250517] Re: gvfs performs slowly on bulk sftp transfers
It seems to be related to this upstream bug report at Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=532951 (slow download using sftp://) ** Bug watch added: GNOME Bug Tracker #532951 https://bugzilla.gnome.org/show_bug.cgi?id=532951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/250517 Title: gvfs performs slowly on bulk sftp transfers To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/250517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015211] [NEW] Ubiquity installed grub-efi when it should have installed grub-pc
Public bug reported: Goal: Create a dual boot system with a pre installed Win7x64 and Ubuntu Desktop 12.04 LTS amd64 with Grub installed as the boot-loader in the MBR of sda. Problem symptoms: After Ubuntu installation from the Live CD along side Win7x64, Grub wont start at boot-up of the system. It boots straight into Win7. Hypothesis: The Ubuntu Desktop 12.04 amd64 Live CD, was booted with an UEFI boot sequence although the hard disk structure is MSDOS with MBR. This fools ubuquity into installing Grub in EFI mode and does not install grub-pc into the MBR. For full information please view: http://ubuntuforums.org/showthread.php?p=12030957#post12030957 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: efi uefi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015211] Re: Ubiquity installed grub-efi when it should have installed grub-pc
** Attachment added: syslog and partman log files from the installer https://bugs.launchpad.net/bugs/1015211/+attachment/3196276/+files/installer-logs.7z -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903741] [NEW] QuteCom Crashes after a few seconds
Public bug reported: I start qutecom on a machine and it crashes a few seconds later, this happened overnight and I have updated all the machines to the latest versions and the error is still there. I have tested over 20, with Ubuntu 11.10 and with 10.04 LTS version too! PLEASE HELP! mm@mm-desktop:~$ qutecom (info) 11:25:26 [Common] void QtLanguage::loadLanguageFromConfig(): no Qt translation available for locale 'en_US' *** longjmp causes uninitialized stack frame ***: qutecom terminated === Backtrace: = /lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x45)[0x57e98d5] /lib/i386-linux-gnu/libc.so.6(+0xe784a)[0x57e984a] /lib/i386-linux-gnu/libc.so.6(__longjmp_chk+0x4b)[0x57e97bb] /usr/lib/i386-linux-gnu/libcurl.so.4(+0xa0e5)[0x79d0e5] [0x9d9400] [0x9d9416] /lib/i386-linux-gnu/libc.so.6(__poll+0x7e)[0x57c540e] /lib/i386-linux-gnu/libglib-2.0.so.0(g_poll+0x2b)[0x183a34b] /lib/i386-linux-gnu/libglib-2.0.so.0(+0x43896)[0x182b896] /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x6a)[0x182bc2a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6a)[0x556ada] /usr/lib/i386-linux-gnu/libQtGui.so.4(+0x20fe3a)[0xf31e3a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4d)[0x5271dd] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xa1)[0x527421] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN7QDialog4execEv+0x109)[0x13b17c9] qutecom(_ZN20QtUserProfileHandler15showLoginWindowEv+0x6f)[0x82431ff] qutecom(_ZN20QtUserProfileHandler39noCurrentUserProfileSetEventHandlerSlotEv+0x1b)[0x824329b] qutecom(_ZN20QtUserProfileHandler11qt_metacallEN11QMetaObject4CallEiPPv+0x248)[0x81b8268] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QMetaObject8metacallEP7QObjectNS_4CallEiPPv+0x3d)[0x52eb7d] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x35)[0x539685] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x272)[0x540b52] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xc4)[0xe79d54] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x173)[0xe7f103] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x52819e] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x313)[0x52bf93] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2c)[0x52c0ec] /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x1946a4)[0x5566a4] /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x1df)[0x182b25f] /lib/i386-linux-gnu/libglib-2.0.so.0(+0x43990)[0x182b990] /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x6a)[0x182bc2a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6a)[0x556ada] /usr/lib/i386-linux-gnu/libQtGui.so.4(+0x20fe3a)[0xf31e3a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4d)[0x5271dd] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xa1)[0x527421] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9d)[0x52c19d] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN12QApplication4execEv+0x24)[0xe778f4] qutecom(_ZN9QtFactory4execEv+0x14)[0x81f3a04] qutecom(main+0xcda)[0x81a8d8a] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x571b113] qutecom[0x81b2981] === Memory map: 0011-00163000 r-xp 08:03 5255900 /usr/lib/i386-linux-gnu/libQtSvg.so.4.7.4 00163000-00164000 r--p 00052000 08:03 5255900 /usr/lib/i386-linux-gnu/libQtSvg.so.4.7.4 00164000-00165000 rw-p 00053000 08:03 5255900 /usr/lib/i386-linux-gnu/libQtSvg.so.4.7.4 00165000-00167000 r-xp 08:03 525951 /usr/lib/qutecom/libpsiidle.so 00167000-00168000 r--p 2000 08:03 525951 /usr/lib/qutecom/libpsiidle.so 00168000-00169000 rw-p 3000 08:03 525951 /usr/lib/qutecom/libpsiidle.so 00169000-0016d000 r-xp 08:03 5767993 /lib/i386-linux-gnu/libuuid.so.1.3.0 0016d000-0016e000 r--p 3000 08:03 5767993 /lib/i386-linux-gnu/libuuid.so.1.3.0 0016e000-0016f000 rw-p 4000 08:03 5767993 /lib/i386-linux-gnu/libuuid.so.1.3.0 0016f000-00171000 r-xp 08:03 5245271 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 00171000-00172000 r--p 1000 08:03 5245271 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 00172000-00173000 rw-p 2000 08:03 5245271 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 00173000-00183000 r-xp 08:03 525938 /usr/lib/qutecom/libowmemorydump.so 00183000-00184000 r--p f000 08:03 525938 /usr/lib/qutecom/libowmemorydump.so 00184000-00185000 rw-p 0001 08:03 525938 /usr/lib/qutecom/libowmemorydump.so
[Bug 903741] Re: QuteCom Crashes after a few seconds
** Description changed: - I start qutecom on a machine, i have tested over 20, with Ubuntu 11.10 - and with 10.04 LTS version too! + I start qutecom on a machine and it crashes a few seconds later, i have + tested over 20, with Ubuntu 11.10 and with 10.04 LTS version too! PLEASE HELP! mm@mm-desktop:~$ qutecom (info) 11:25:26 [Common] void QtLanguage::loadLanguageFromConfig(): no Qt translation available for locale 'en_US' *** longjmp causes uninitialized stack frame ***: qutecom terminated === Backtrace: = /lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x45)[0x57e98d5] /lib/i386-linux-gnu/libc.so.6(+0xe784a)[0x57e984a] /lib/i386-linux-gnu/libc.so.6(__longjmp_chk+0x4b)[0x57e97bb] /usr/lib/i386-linux-gnu/libcurl.so.4(+0xa0e5)[0x79d0e5] [0x9d9400] [0x9d9416] /lib/i386-linux-gnu/libc.so.6(__poll+0x7e)[0x57c540e] /lib/i386-linux-gnu/libglib-2.0.so.0(g_poll+0x2b)[0x183a34b] /lib/i386-linux-gnu/libglib-2.0.so.0(+0x43896)[0x182b896] /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x6a)[0x182bc2a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6a)[0x556ada] /usr/lib/i386-linux-gnu/libQtGui.so.4(+0x20fe3a)[0xf31e3a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4d)[0x5271dd] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xa1)[0x527421] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN7QDialog4execEv+0x109)[0x13b17c9] qutecom(_ZN20QtUserProfileHandler15showLoginWindowEv+0x6f)[0x82431ff] qutecom(_ZN20QtUserProfileHandler39noCurrentUserProfileSetEventHandlerSlotEv+0x1b)[0x824329b] qutecom(_ZN20QtUserProfileHandler11qt_metacallEN11QMetaObject4CallEiPPv+0x248)[0x81b8268] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QMetaObject8metacallEP7QObjectNS_4CallEiPPv+0x3d)[0x52eb7d] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x35)[0x539685] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x272)[0x540b52] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xc4)[0xe79d54] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x173)[0xe7f103] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x52819e] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x313)[0x52bf93] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2c)[0x52c0ec] /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x1946a4)[0x5566a4] /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x1df)[0x182b25f] /lib/i386-linux-gnu/libglib-2.0.so.0(+0x43990)[0x182b990] /lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x6a)[0x182bc2a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6a)[0x556ada] /usr/lib/i386-linux-gnu/libQtGui.so.4(+0x20fe3a)[0xf31e3a] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4d)[0x5271dd] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xa1)[0x527421] /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9d)[0x52c19d] /usr/lib/i386-linux-gnu/libQtGui.so.4(_ZN12QApplication4execEv+0x24)[0xe778f4] qutecom(_ZN9QtFactory4execEv+0x14)[0x81f3a04] qutecom(main+0xcda)[0x81a8d8a] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x571b113] qutecom[0x81b2981] === Memory map: 0011-00163000 r-xp 08:03 5255900 /usr/lib/i386-linux-gnu/libQtSvg.so.4.7.4 00163000-00164000 r--p 00052000 08:03 5255900 /usr/lib/i386-linux-gnu/libQtSvg.so.4.7.4 00164000-00165000 rw-p 00053000 08:03 5255900 /usr/lib/i386-linux-gnu/libQtSvg.so.4.7.4 00165000-00167000 r-xp 08:03 525951 /usr/lib/qutecom/libpsiidle.so 00167000-00168000 r--p 2000 08:03 525951 /usr/lib/qutecom/libpsiidle.so 00168000-00169000 rw-p 3000 08:03 525951 /usr/lib/qutecom/libpsiidle.so 00169000-0016d000 r-xp 08:03 5767993 /lib/i386-linux-gnu/libuuid.so.1.3.0 0016d000-0016e000 r--p 3000 08:03 5767993 /lib/i386-linux-gnu/libuuid.so.1.3.0 0016e000-0016f000 rw-p 4000 08:03 5767993 /lib/i386-linux-gnu/libuuid.so.1.3.0 0016f000-00171000 r-xp 08:03 5245271 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 00171000-00172000 r--p 1000 08:03 5245271 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 00172000-00173000 rw-p 2000 08:03 5245271 /usr/lib/i386-linux-gnu/libXau.so.6.0.0 00173000-00183000 r-xp 08:03 525938 /usr/lib/qutecom/libowmemorydump.so 00183000-00184000 r--p f000
[Bug 806950] Re: HP Laserjet M1212nf scanning freezes-up after first scan over a networkconnection (hpaio)
Dear IKT, Yes, deleting the print queues and recreating the printer with hp-setup works. It still baffles me, why it has to be done twice for scanning to work correctly? Thanks for your help. Summarizing: After initial installation scanning freezes up after the first scan. To fix it: delete the print queues run hp-setup again and select the printer again as your preferred printer (this recreates the print queues). All should work fine (printing, scanning and faxing) after recreating the print queues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806950 Title: HP Laserjet M1212nf scanning freezes-up after first scan over a networkconnection (hpaio) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/806950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806950] Re: HP Laserjet M1212nf scanning freezes-up after first scan over a networkconnection (hpaio)
** Description changed: It seems that after scanning with xsane it leaves the printer in an odd state that requires a printer reset to get scanning working again. After thorough testing I am sure, that scanning from Ubuntu Linux 10.04.2LTS with hp-scan or xsane only works once and then the printer needs to be reset/power cycled. Even trying to scan with another machine/OS like Windoze doesn't work anymore until the printer is reset. When initially scanning from Windoze, it does not leave the printer in an odd state, so multiple consecutive scans are no problem, but as soon as I do one scan with xsane from Linux the first scan succeeds but then the scanning capability of the printer stops working. - Printer type: HP LaserJet m1212nf (a HP LaserJet M1210 series printer) - Printer Firmware Datecode: 20110512 + Printer type: HP LaserJet m1212nf (a HP LaserJet M1210 series printer) + Printer Firmware Datecode: 20110512 Connection: network connection hpaio - I get the following error when trying to capture a scan again: - Using device hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=HP - Opening connection to device... - error: SANE: Error during device I/O (code=9) + I get the following error when trying to capture a scan again: + Using device hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=HP + Opening connection to device... + error: SANE: Error during device I/O (code=9) - The product specifications of the printer note that it does support TWAIN: - Quote Scanning specifications: - * Scan from TWAIN-compliant or Windows Imaging Application (WIA)-compliant software. - * Scan from a computer by using HP LaserJet Scan software for Windows or by using HP Director software for Mac. - * TWAIN VERSION: Version 1.9 + The product specifications of the printer note that it does support TWAIN: + Quote Scanning specifications: + * Scan from TWAIN-compliant or Windows Imaging Application (WIA)-compliant software. + * Scan from a computer by using HP LaserJet Scan software for Windows or by using HP Director software for Mac. + * TWAIN VERSION: Version 1.9 - I'm using HPLIP version: 3.10.4 + I'm using HPLIP version: 3.11.5 - Furthermore, + Furthermore, http://hplipopensource.com/hplip-web/models/laserjet/hp_laserjet_professional_m1212nf_mfp.html Says that scanning should work using HPLIP v3.10.4 with Ubuntu 10.04LTS. This bug was previously submitted at the SANE project site, but after their analysis they concluded that they do not produce the hpaio backend. It is part of the hplip project and I should ask here. (see: https://alioth.debian.org/tracker/index.php?func=detailaid=313207group_id=30186atid=410366 ) I hope you are able to resolve this issue? Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806950 Title: HP Laserjet M1212nf scanning freezes-up after first scan over a networkconnection (hpaio) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/806950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806950] Re: HP Laserjet M1212nf scanning freezes-up after first scan over a networkconnection (hpaio)
** Also 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/806950 Title: HP Laserjet M1212nf scanning freezes-up after first scan over a networkconnection (hpaio) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/806950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109701] Re: [needs-packaging] TrueCrypt
Please review the new license version, because manually updating is becoming a hassle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/109701 Title: [needs-packaging] TrueCrypt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160516] Re: [hardy] ImportError: No module named gtk.SoftwarePropertiesGtk
Same problem here! I am using Gutsy with Gutsy reps, but these were manually changed back to Gutsy after having used Hardy for a while (since I did that, a few parts of the system has been performing poorly). -- [hardy] ImportError: No module named gtk.SoftwarePropertiesGtk https://bugs.launchpad.net/bugs/160516 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 147298] Re: AD198x Analog: microphone misconfigured
I have a zepto znote 3415 with the same sound card. I only got sound working through a long workaround, but capture still does not work. I get the error message when testing sound input. Doing gst-launch gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat in a terminal shows the same messages but I can't hear any input. -- AD198x Analog: microphone misconfigured https://bugs.launchpad.net/bugs/147298 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 130559] Re: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) - no sound
I have a Zepto Znote 3415, with this soundcard, and no sound. Using good headphones does not let me hear anything, otherwise the outputs are as above (for festuc). I have a santa rosa processor with the intel chipset, just like festuc. I'm willing to give outputs and to help in any way. -- Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) - no sound https://bugs.launchpad.net/bugs/130559 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
