[Bug 1950029] [NEW] Suspend "Wait until snapd is fully seeded"
Public bug reported: Using Lenovo IdeaPad 3i Gaming, I got a software update this morning, and since that time, impossible to complete a power suspend. It is always blocked after the message "Finished Wait until snapd is fully seeded". Power Down is working well. Logout is working well. Only the Suspend action is blocked on this message mentioned above. - It is a regression bug, it was not happening before the latest update. - Reproduced by following ways to suspend the computer : - systemctl suspend - Via Ubuntu down arrow on top left menu bar, Power Down / Logout --> Suspend. - Closing the lid Bug reported with 'ubuntu-bug linux' cf picture in attachment on all messages seen before the system gets hanged with the final "Finished Wait until snapd is fully seeded" message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 17:50:25 2021 InstallationDate: Installed on 2021-04-26 (193 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Terminal messages on Suspend action" https://bugs.launchpad.net/bugs/1950029/+attachment/5538501/+files/IMG_20211105_143122.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950029 Title: Suspend "Wait until snapd is fully seeded" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1950029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946387] [NEW] Ubuntu won't install beside Mint
Public bug reported: Tried installing Mint beside Windows at the beginning. Could only access Mint from bios after installation, or Windows, by changing boot order. Tried installing Ubuntu beside Mint to see if that made a difference. Now, when I boot (with f1} I only get boot order Ubuntu and Windows boot manager and neither one boots up, just comes back to the boot order no matter what I so. Booted from Windows recovery usb and just would not recover no matter what option I picked. Figured Windows was toast so formatted any windows partition (From the Ubuntu install disk after loading and trying Ubuntu as the option and going to Disks} and deleted those partitions to turn them into unused space. Rebooted and reloaded Ubuntu install disk and tried an install beside Mint, which still appeared to be there. No dice.Still won't boot unless I hit f1 and then defaults to just the boot order of Ubuntu and Windows boot manager! Would like to just erase my ssd and start with fresh install of Ubuntu but not sure how to accomplish that unless I use my desktop (That has Windows, Mint and Ubuntu running side by side with Grub showing up at boot to give me the option of OS's} I have another ssd plugged into a usb that I could exchange for this ssd in my laptop and do whatever is necessary to it from there. Or I could just download the Windows 10 ISO from the Microsoft website and start over. Not sure if any of those options are the right ones. HELP! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckMismatches: ./dists/focal/main/binary-amd64/Packages.gz CasperMD5CheckResult: skip CasperVersion: 1.445.1 Date: Thu Oct 7 13:39:41 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946387 Title: Ubuntu won't install beside Mint To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1946387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898405] [NEW] Ubuntu 20.04 update from 18.04 freezed then partial_update fails
Public bug reported: - Running on Lubuntu 18.04. - Got software upgrade popup to upgrade to 20.04. - Answered yes, started the update progress. - After about 10 minutes, got a popup window, asking to select one choice only like "lightDM" but impossible to answer as this pop-up window was frozen, everything else was frozen. - Proceeded to turnoff laptop (long push 10s on power button). - Turnon Laptop. - Run manually software updater. - Software Updater indicated previous upgrade failed, proposed to "partially upgrade" --> confirmed yes. - then Error popup message : "Can't install 'lubuntu-core' It was impossible to install a required package. Please report this as a bug using 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal." - Then proceeded to 'ubuntu-bug ubuntu-release-upgrader-core' via Terminal lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:18.04.38 Candidate: 1:20.04.25 Version table: 1:20.04.25 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 1:20.04.18 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages *** 1:18.04.38 100 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: LXDE Date: Sat Oct 3 17:39:27 2020 InstallationDate: Installed on 2018-09-11 (753 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898405 Title: Ubuntu 20.04 update from 18.04 freezed then partial_update fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884008] [NEW] network manager prefers further away AP when there are multiple APs
Public bug reported: I'm on Ubuntu 20.04. My Wifi set-up has multiple access points throughout my home, and they all have the same SSID. It doesn't matter where I am in my home though, network manager always connects to one particular AP. If I list all the access points with `nmcli dev wifi list` I can see that it even picks that one access point if it is the farthest away one: 76:83:C2:BB:34:2A -- Infra 36405 Mbit/s 97 ▂▄▆█ WPA2 74:83:C2:BB:34:2A my_access_point Infra 36405 Mbit/s 95 ▂▄▆█ WPA2 74:83:C2:BA:34:2A my_access_point Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 76:83:C2:BA:34:2A -- Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 B6:FB:E4:45:CA:82 -- Infra 157 405 Mbit/s 44 ▂▄__ WPA2 * B4:FB:E4:45:CA:82 my_access_point Infra 157 405 Mbit/s 44 ▂▄__ WPA2 B6:FB:E4:44:CA:82 -- Infra 11195 Mbit/s 42 ▂▄__ WPA2 B4:FB:E4:44:CA:82 my_access_point Infra 11195 Mbit/s 40 ▂▄__ WPA2 It is true that if I change the BSSID field in the wifi settings I can get it to connect to a particular one, but that is not sufficient. I have a laptop, and if I move around my home I need it to connect to the closest one, and switching manually to whichever one is closest is not practical. I can't even create multiple entries for each BSSID in the list of networks, if I try many different networks appear with the same name and random numbers and I can't even label them. This is network manager version 1.22.10-1ubuntu2.1 ** Affects: network-manager (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/1884008 Title: network manager prefers further away AP when there are multiple APs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791425]
It seems to be fixed on the last version available on wandbox.org (gcc HEAD 9.0.1 201904): https://wandbox.org/permlink/Tu4T8jEXDDtDw0OS Though it doesn't work on any other versions (8.3.0...). Any chance to see the fix in the 8 branch? Anyway, thanks a lot :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791425 Title: Compiler error: constexpr with bitfields. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc-defaults/+bug/1791425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796682] [NEW] just trying to upgrade
Public bug reported: oijok;l ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CasperVersion: 1.380 Date: Mon Oct 8 09:04:29 2018 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lubuntu ubiquity-17.04.9 zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796682 Title: just trying to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1796682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784117] Re: Steam fails to start: glxChooseVisual failed
Hello, This is still happening on ubuntu 18.04.1 with nvidia-driver-410. Purging nvidia-drivers, steam, rebooting and reinstalling both does not solve the issue. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784117 Title: Steam fails to start: glxChooseVisual failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1784117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773700] [NEW] [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
Public bug reported: I just installed ubuntu, and immediately had problems of very loud and crackling sound no matter what sound I played. I tried the three solutions listed here https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in no sound at all, and now even if I revert back everything, I can't get any sound out from the speakers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: remuth 1038 F...m pulseaudio /dev/snd/controlC0: remuth 1038 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 27 22:37:20 2018 InstallationDate: Installed on 2018-05-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: remuth 1038 F...m pulseaudio /dev/snd/controlC0: remuth 1038 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773700 Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687174] Re: no wifi after software update on Dell Latitude D630
Hi again, After few updates and reboots, I noticed Wifi started to see Access Point and started to work again. I am not sure what update could fix the issue. tail -n25 /var/log/apt/history.log /var/log/apt/history.log Start-Date: 2017-05-02 21:09:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.327' Install: linux-image-4.4.0-77-generic:amd64 (4.4.0-77.98, automatic), linux-image-extra-4.4.0-77-generic:amd64 (4.4.0- 77.98, automatic), linux-headers-4.4.0-77-generic:amd64 (4.4.0-77.98, automatic), linux-headers-4.4.0-77:amd64 (4.4.0- 77.98, automatic) Upgrade: libreoffice-style-breeze:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-math :amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), linux-headers-generic:amd64 (4.4.0.75.81, 4.4.0.7 7.83), linux-libc-dev:amd64 (4.4.0-75.96, 4.4.0-77.98), python3-software-properties:amd64 (0.96.20.5, 0.96.20.6), sane -utils:amd64 (1.0.25+git20150528-1ubuntu2, 1.0.25+git20150528-1ubuntu2.16.04.1), linux-image-generic:amd64 (4.4.0.75.8 1, 4.4.0.77.83), libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libicu55:amd64 ( 55.1-7ubuntu0.1, 55.1-7ubuntu0.2), libicu55:i386 (55.1-7ubuntu0.1, 55.1-7ubuntu0.2), libreoffice-gtk:amd64 (1:5.1.6~rc 2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-style-human:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1. 6~rc2-0ubuntu1~xenial2), google-chrome-stable:amd64 (58.0.3029.81-1, 58.0.3029.96-1), libsane-dev:amd64 (1.0.25+git201 50528-1ubuntu2, 1.0.25+git20150528-1ubuntu2.16.04.1), software-properties-gtk:amd64 (0.96.20.5, 0.96.20.6), python3-un o:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-style-galaxy:amd64 (1:5.1.6~rc2-0ubu ntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-base-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0u buntu1~xenial2), libreoffice-ogltrans:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice- impress:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), ure:amd64 (5.1.6~rc2-0ubuntu1~xenial1, 5.1 .6~rc2-0ubuntu1~xenial2), libreoffice-writer:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libre office-common:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libsane-common:amd64 (1.0.25+git2015 0528-1ubuntu2, 1.0.25+git20150528-1ubuntu2.16.04.1), fonts-opensymbol:amd64 (2:102.7+LibO5.1.6~rc2-0ubuntu1~xenial1, 2 :102.7+LibO5.1.6~rc2-0ubuntu1~xenial2), libreoffice-pdfimport:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu 1~xenial2), uno-libs3:amd64 (5.1.6~rc2-0ubuntu1~xenial1, 5.1.6~rc2-0ubuntu1~xenial2), libreoffice-gnome:amd64 (1:5.1.6 ~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-calc:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc 2-0ubuntu1~xenial2), linux-generic:amd64 (4.4.0.75.81, 4.4.0.77.83), libsane:amd64 (1.0.25+git20150528-1ubuntu2, 1.0.2 5+git20150528-1ubuntu2.16.04.1), libreoffice-draw:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-avmedia-backend-gstreamer:amd64 (1:5.1.6~rc2-0ubuntu1~xenial1, 1:5.1.6~rc2-0ubuntu1~xenial2), software-pro perties-common:amd64 (0.96.20.5, 0.96.20.6) End-Date: 2017-05-02 21:30:13 Start-Date: 2017-05-05 22:49:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.247' Upgrade: passwd:amd64 (1:4.2-3.1ubuntu5, 1:4.2-3.1ubuntu5.2), login:amd64 (1:4.2-3.1ubuntu5, 1:4.2-3.1ubuntu5.2) End-Date: 2017-05-05 22:50:22 I really do not see what could have cause Wifi not to work between April 28th update and today (May 8th). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687174 Title: no wifi after software update on Dell Latitude D630 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1687174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641055] Re: startx, lightdm fail to start
After deleting the .Xauthority file, I can now successfully log into a Unity session. The problem seems to be gone (rebooting worked fine after this). Maybe somebody can figure out how I got into this situation, but otherwise the bug can be closed as far as I'm concerned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641055 Title: startx, lightdm fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641055] Re: startx, lightdm fail to start
If I *remove* xserver-xorg-video-intel, lightdm is able to show me the login screen. However, there is corruption on the screen and trying to log into a Unity or Gnome session just shows a blank screen and then puts me back into the login screen after 1 second. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641055 Title: startx, lightdm fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641055] [NEW] startx, lightdm fail to start
Public bug reported: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 Uname: Linux 4.8.7-040807-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 11 09:07:35 2016 DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: acpi_call, 1.0, 3.2.0-21-generic, x86_64: built tp_smapi, 0.42, 4.4.0-47-generic, x86_64: installed tp_smapi, 0.42, 4.8.0-27-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2011-03-11 (2071 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 20BWS02D00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.7-040807-lowlatency root=UUID=45e540a8-fe2a-49e7-9c27-99725af4a6bd ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to yakkety on 2016-11-10 (0 days ago) dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BWS02D00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS02D00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.71+git1611081830.670f1e~gd~y version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1611101930.f500c3~gd~y version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.1~git1611101930.f500c3~gd~y version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Nov 11 09:06:56 2016 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641055 Title: startx, lightdm fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563155] Re: No Application Data Found
Tried #3 and #5 but it didn't help. I attached the output 'gnome-software' prints when started. I think these bugs are related: https://bugs.launchpad.net/bugs/1573052 https://bugs.launchpad.net/bugs/1573453 ** Attachment added: "output.log" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1563155/+attachment/4645012/+files/output.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563155 Title: No Application Data Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1563155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478217] Re: can't pair bluetooth keyboard, phone doesn't show code.
I've got a Logitech K810 keyboard but unlike in this bug, no PIN prompt will be shown, it will appear in the connected devices, but the connectivity lights will keep flashing and keypresses will not do anything. Do you think this is a separate issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478217 Title: can't pair bluetooth keyboard, phone doesn't show code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1478217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332648] [NEW] Wrong bluetooth pairing PIN reported for Logitech K810
Public bug reported: I've been unable to pair my Logitech K810. I figured out that the new device setup wizard reports the wrong PIN. I used bluez-hcidump before trying to pair from the setup wizard. The setup wizard PIN differs from the one reported by bluez-hcidump. The PIN reported by bluez-hcidump was correct. Here's the command I used: sudo hcidump -at | grep pass 1) Ubuntu release: Ubuntu 14.04 LTS 2) Package version: 3.8.2.1-0ubuntu4 3) What I expected to happen: I expected to see the same bluetooth pairing PIN as in bluez-hcidump. 4) What happened instead: Some PIN whose origin I do not know was reported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-bluetooth 3.8.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 20 19:19:48 2014 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: I've been unable to pair my Logitech K810. I figured out that the new device setup wizard reports the wrong PIN. I used bluez-hcidump before trying to pair from the setup wizard. The setup wizard PIN differs from the one reported by bluez-hcidump. The PIN reported by bluez-hcidump was correct. Here's the command I used: sudo hcidump -at | grep pass 1) Ubuntu release: Ubuntu 14.04 LTS 2) Package version: 3.8.2.1-0ubuntu4 3) What I expected to happen: I expected to see the same bluetooth pairing PIN as in bluez-hcidump. 4) What happened instead: - Some PIN whose orgin I do not know was reported. + Some PIN whose origin I do not know was reported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-bluetooth 3.8.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 20 19:19:48 2014 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332648 Title: Wrong bluetooth pairing PIN reported for Logitech K810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1332648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332648] Re: Wrong bluetooth pairing PIN reported for Logitech K810
** Description changed: I've been unable to pair my Logitech K810. I figured out that the new device setup wizard reports the wrong PIN. I used bluez-hcidump before trying to pair from the setup wizard. The setup wizard PIN differs from the one reported by bluez-hcidump. The PIN reported by bluez-hcidump was correct. Here's the command I used: sudo hcidump -at | grep pass + + Bluetooth module (probably not relevant): + (Intel?) Bluetooth 4.0, 3.0+HS, 2.1+EDR + Not entirely sure as the specs for my Gigabyte GA-F2A88XN-WIFI motherboard were unclear. 1) Ubuntu release: Ubuntu 14.04 LTS 2) Package version: 3.8.2.1-0ubuntu4 3) What I expected to happen: I expected to see the same bluetooth pairing PIN as in bluez-hcidump. 4) What happened instead: Some PIN whose origin I do not know was reported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-bluetooth 3.8.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 20 19:19:48 2014 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332648 Title: Wrong bluetooth pairing PIN reported for Logitech K810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1332648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332648] Re: Wrong bluetooth pairing PIN reported for Logitech K810
** Description changed: I've been unable to pair my Logitech K810. I figured out that the new device setup wizard reports the wrong PIN. I used bluez-hcidump before trying to pair from the setup wizard. The setup wizard PIN differs from the one reported by bluez-hcidump. The PIN reported by bluez-hcidump was correct. Here's the command I used: sudo hcidump -at | grep pass + + Minimal steps to reproduce: + 1. Run Configure new device... from the bluetooth applet menu + 2. Install bluez-hcidump. + 3. Put the keyboard in pairing mode (button underneath) and pick profile (F1, F2 or F3) + 4. Run 'sudo hcidump -at | grep pass' from the terminal + 5. Select the keyboard from the list of devices in the setup wizard and continue + 6. Observe how the PIN differs from the one in hcidump. Bluetooth module (probably not relevant): (Intel?) Bluetooth 4.0, 3.0+HS, 2.1+EDR Not entirely sure as the specs for my Gigabyte GA-F2A88XN-WIFI motherboard were unclear. 1) Ubuntu release: Ubuntu 14.04 LTS 2) Package version: 3.8.2.1-0ubuntu4 3) What I expected to happen: I expected to see the same bluetooth pairing PIN as in bluez-hcidump. 4) What happened instead: Some PIN whose origin I do not know was reported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-bluetooth 3.8.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 20 19:19:48 2014 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332648 Title: Wrong bluetooth pairing PIN reported for Logitech K810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1332648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
Swâmi, We've all laid out these arguments many times over. Yes, this issue is frustrating (and I regret having vented some of my own frustration in my first comments) but let's keep it civil. There are proposed solutions. I, for one, think Andreas' proposal is the best way out of the current dead lock as it would allow each and everyone of us to configure the fr-oss layout the way we want it. It's now up to Sergey and Nicolas to decide how to move this forward. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
Swâmi, We've all laid out these arguments many times over. Yes, this issue is frustrating (and I regret having vented some of my own frustration in my first comments) but let's keep it civil. There are proposed solutions. I, for one, think Andreas' proposal is the best way out of the current dead lock as it would allow each and everyone of us to configure the fr-oss layout the way we want it. It's now up to Sergey and Nicolas to decide how to move this forward. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
Nicolas, Where does the need to *have* a key for nbsp come from? Isn't a compose combo more appropriate and less error-prone? Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
Nicolas, Where does the need to *have* a key for nbsp come from? Isn't a compose combo more appropriate and less error-prone? Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
I'm at a loss as to what to do to help find a solution for everyone. fr-oss is a great layout with many useful improvements over fr-latin9, but the missing ControlR is a deal breaker. I'm personally back to using the default fr layout and I'll advise users to do the same if they want their ControlR back. @Ubuntu users listening in through Launchpad: use whatever control panel you have to select a layout that doesn't have the words Alternative or variante. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
I'm at a loss as to what to do to help find a solution for everyone. fr-oss is a great layout with many useful improvements over fr-latin9, but the missing ControlR is a deal breaker. I'm personally back to using the default fr layout and I'll advise users to do the same if they want their ControlR back. @Ubuntu users listening in through Launchpad: use whatever control panel you have to select a layout that doesn't have the words Alternative or variante. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315938] [NEW] Lost screen
Public bug reported: I regularly lost image on my screen. This happen instantly and I believe this is a graphic card issue with Ubuntu since it work correctly with Windows. I get stuck with vertical lines grey/blue screen image and the only solution is to restart the computer. No more icons, mouse pointer or anything else. This is my first try with Linux, with Ubuntu 14.04 LTS on a desktop with 2,2 Ghz processor; 250 Gb hard disk; 1Gb RAM and ATI Radeon Xpress 200 card. I don't have this problem with Windows XP on the same computer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 4 15:57:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8185] InstallationDate: Installed on 2014-04-21 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4b5c43ab-073d-4bdb-bef8-c2988cf57157 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A8R-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd04/06/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8R-MX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun May 4 15:54:39 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315938 Title: Lost screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1315938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
(In reply to comment #60) Gentlemen, I am really stuck at that point. Allow me to sum it up. - Nicolas is the sole advocate of having Control_R mapped to Level5. - The rest of us want to go back to having both left and right Control behaving the same way. I'm not quite sure how you want us to organize a vote or poll. French Linux users (just like non-French ones) use a variety of distributions (which, BTW, may not ship the changed version of xkeyboard-config), and may not even all use a French keyboard (I'd say roughly half of my Linux-using friends and coworkers are using US qwerty layouts or mac layouts). Since apparently no hardware maker is following ISO standards, may I suggest creating new layouts such as oss-iso with Nicolas' changes? As one of Gentoo's X11 maintainers, I am really tempted to just revert that change downstream. The few French users I have talked to were just as surprised as I was to lose their Control_R key for no apparent reason. I could organize a poll on my blog but being aggregated only on Planet Gentoo, I wouldn't give much credit to any numbers I could find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
(In reply to comment #60) Gentlemen, I am really stuck at that point. Allow me to sum it up. - Nicolas is the sole advocate of having Control_R mapped to Level5. - The rest of us want to go back to having both left and right Control behaving the same way. I'm not quite sure how you want us to organize a vote or poll. French Linux users (just like non-French ones) use a variety of distributions (which, BTW, may not ship the changed version of xkeyboard-config), and may not even all use a French keyboard (I'd say roughly half of my Linux-using friends and coworkers are using US qwerty layouts or mac layouts). Since apparently no hardware maker is following ISO standards, may I suggest creating new layouts such as oss-iso with Nicolas' changes? As one of Gentoo's X11 maintainers, I am really tempted to just revert that change downstream. The few French users I have talked to were just as surprised as I was to lose their Control_R key for no apparent reason. I could organize a poll on my blog but being aggregated only on Planet Gentoo, I wouldn't give much credit to any numbers I could find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292434] [NEW] rsyslog cannot start from /etc/init.d
Public bug reported: Hi folks, I am running rsyslog on the new Trusty and I got the issue starting the process with old init.d system: - root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is running root@trusty01:~# /etc/init.d/rsyslog stop root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is running root@trusty01:~# service rsyslog stop rsyslog stop/waiting root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is not running root@trusty01:~# /etc/init.d/rsyslog start root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is not running root@trusty01:~# service rsyslog start rsyslog start/running, process 1130 - About the package I am running : rsyslog 7.4.4-1ubuntu2amd64 on Release: 14.04 I would expect it either to stop and start the daemon correctly or to exit with a nice error message saying I am deprecated, please use ... Thanks, Remi Debay ** Affects: rsyslog (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/1292434 Title: rsyslog cannot start from /etc/init.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1292434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207589]
Hello! I'm on debian sid with ktorrent 4.3.1-2 installed from a while. I never had this problem until recently, but ktorrent has not been upgraded. So, I guess it is a bug from a recent update of KDE (I'm on KDE 4.11.6-3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207589 Title: ktorrent fails to unzip peerguardian filter file To manage notifications about this bug go to: https://bugs.launchpad.net/ktorrent/+bug/1207589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
For some reason, I found myself using the 'fr oss' layout in Gnome 3.10. And I must say that finding out that this layout was picked as the default left me speechless: two keys on my keyboard no longer behave according to what's *on* the actual key: - the right control key, which just says Ctrl, just like its left counterpart, - and the keypad's del/dot key which has an actual dot on it, not a comma Both of those changes are incomprehensible. Whether *alternative* layouts exist to provide new mappings is of no issue to me. But a layout touted as the default layout should respect what's *engraved* on keyboards. FTR, the original 'fr' layout also has that keypad dot/comma issue but not the right control mapped to Level5, but at least there's an kpdl:dot option to fix the former. So I fumbled through Gnome's ever- changing control panel and managed to change back to it. (In reply to comment #46) For me it does. My keyboard has an Alt Gr label on the AltR key, so it indeed is expected to behave differently from Alt_L, but my ControlR key is labeled as Ctrl, just like the ControlL key. And all other keyboards and OSes I ever used did handle ControlR the same as ControlL, as far as I was concerned as a user. +1, all the French PC keyboards I have owned for the past 15 years have been like this. I can only add my voice to let it be known that having to fix my keyboard layout for correct operation was quite upsetting. Anyhow, thanks to all for looking into it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
For some reason, I found myself using the 'fr oss' layout in Gnome 3.10. And I must say that finding out that this layout was picked as the default left me speechless: two keys on my keyboard no longer behave according to what's *on* the actual key: - the right control key, which just says Ctrl, just like its left counterpart, - and the keypad's del/dot key which has an actual dot on it, not a comma Both of those changes are incomprehensible. Whether *alternative* layouts exist to provide new mappings is of no issue to me. But a layout touted as the default layout should respect what's *engraved* on keyboards. FTR, the original 'fr' layout also has that keypad dot/comma issue but not the right control mapped to Level5, but at least there's an kpdl:dot option to fix the former. So I fumbled through Gnome's ever- changing control panel and managed to change back to it. (In reply to comment #46) For me it does. My keyboard has an Alt Gr label on the AltR key, so it indeed is expected to behave differently from Alt_L, but my ControlR key is labeled as Ctrl, just like the ControlL key. And all other keyboards and OSes I ever used did handle ControlR the same as ControlL, as far as I was concerned as a user. +1, all the French PC keyboards I have owned for the past 15 years have been like this. I can only add my voice to let it be known that having to fix my keyboard layout for correct operation was quite upsetting. Anyhow, thanks to all for looking into it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266310] Re: impossible to scan all pages from feeder with HP OfficeJet 6310
Hi, I made one more test today. Went to simple-scan preference window (Menu Document-- Preferences). Scan side option was Front and back. I changed it to Front only. Then the Scan all pages from feeder indeed now scan all pages, but after last page, the printer does not stop and shows Scanning forever until I close simple-scan program. So this is a progress, manipulating preferences options in the GUI, but not yet completely fixed. we have to dig more on this for this printer family 6310. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266310 Title: impossible to scan all pages from feeder with HP OfficeJet 6310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1266310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266310] Re: impossible to scan all pages from feeder with HP OfficeJet 6310
Hi again, sorry I was busy those last few days. Here is the result of your suggest command : scanimage --all-options scanimage --all-options All options specific to device `hpaio:/usb/Officejet_6300_series?serial=CN86AFV38X04J5': Scan mode: --mode Lineart|Gray|Color [Color] Selects the scan mode (e.g., lineart, monochrome, or color). --resolution 75|100|150|200|300|600dpi [75] Sets the resolution of the scanned image. Advanced: --contrast -127..127 [0] Controls the contrast of the acquired image. --brightness -127..127 [0] Controls the brightness of the acquired image. --compression None|JPEG [JPEG] Selects the scanner compression method for faster scans, possibly at the expense of image quality. --jpeg-quality 0..100 [10] Sets the scanner JPEG compression factor. Larger numbers mean better compression, and smaller numbers mean better image quality. --batch-scan[=(yes|no)] [no] Enables continuous scanning with automatic document feeder (ADF). --source Auto|Flatbed|ADF [Auto] Selects the scan source (such as a document-feeder). --duplex[=(yes|no)] [no] Enables scanning on both sides of the page. Geometry: --length-measurement Unknown|Approximate|Padded [Padded] Selects how the scanned image length is measured and reported, which is impossible to know in advance for scrollfed scans. -l 0..215.9mm [0] Top-left x position of scan area. -t 0..381mm [0] Top-left y position of scan area. -x 0..215.9mm [215.9] Width of scan-area. -y 0..381mm [381] Height of scan-area. I will now work on getting the source code, trying to run it, and trying to disable options one after the other to see if any is causing issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266310 Title: impossible to scan all pages from feeder with HP OfficeJet 6310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1266310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266310] [NEW] impossible to scan all pages from feeder with HP OfficeJet 6310
Public bug reported: Using on Jan 5th 2013 : Ubuntu 13.10. simplescan 3.10.0-0ubuntu1 sane-utils + libsane (1.0.23-0ubuntu3) libsane-hpaio 3.13.9-1 hplip 3.13.9.1 but was also faulty with 3.10 or 3.11. architecture amd64 Dell lattitude D630 A simple page scan would work but nothing would be scanned via the menu Document ▸ Scan ▸ All Pages From Feeder, or by clicking on the arrow to the right of the Scan button, then choosing All Pages From Feeder. If doing so, command is sent to Hp Officejet 6310 All-in-One Printer Scanner, pop-up appears saying HPLIP Device Status : scan job started (2000), waiting then popup indicates HPLIP Device Status : scan job completed (2001), but Officejet 6310 still indicates Scanning... on the LCD, on button blinks continuously, and nothing happens physically. After a while, I get a red bar on top of Simple Scan window, with following message : Failed to scan Unable to start scan 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description:Ubuntu 13.10 Release:13.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy simple-scan simple-scan: Installed: 3.10.0-0ubuntu1 Candidate: 3.10.0-0ubuntu1 Version table: *** 3.10.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy sane sane: Installed: (none) Candidate: 1.0.14-9 Version table: 1.0.14-9 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages If more infos needed, you can contact me at remi.chart...@netcourrier.com ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: simple-scan 3.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Jan 5 16:25:56 2014 DriverPackageVersions: libsane 1.0.23-0ubuntu3 libsane-extras N/A hplip 3.13.9-1 hpoj N/A InstallationDate: Installed on 2013-09-07 (120 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Latitude D630 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=b79476ae-f2ea-4a66-8983-332a887dd3c4 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to saucy on 2013-10-21 (76 days ago) dmi.bios.date: 11/24/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 saucy simple-scan ** Attachment added: copy screen of simple-scan after scan all page from feeder fails https://bugs.launchpad.net/bugs/1266310/+attachment/3941522/+files/Screenshot%20from%202014-01-05%2016%3A36%3A09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266310 Title: impossible to scan all pages from feeder with HP OfficeJet 6310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1266310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266310] Re: impossible to scan all pages from feeder with HP OfficeJet 6310
2 additional informations : 1st time I launch simple-scan, it takes forever to appear. cf log obtained by simplescan -d : $ simple-scan -d [+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.10.0, PID=11029 [+0.00s] DEBUG: Connecting to session manager [+0.66s] WARNING: g_object_set_valist: invalid object type 'GtkAdjustment' for value type 'GtkWidget' [+0.69s] DEBUG: ui.vala:1513: Restoring window to 600x400 pixels [+0.69s] DEBUG: ui.vala:1518: Restoring window to maximized [+0.77s] DEBUG: autosave-manager.vala:127: Found at least one autosave page, taking ownership [+554.56s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+554.57s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+554.84s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+572.94s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+572.94s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+573.10s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+613.75s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+613.75s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+613.90s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+628.54s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+628.54s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+628.69s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+639.48s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+639.48s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+639.63s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+645.31s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+645.31s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+645.47s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+650.62s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+650.62s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+650.77s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+662.08s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+662.08s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+662.25s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+667.88s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+667.88s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+668.04s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+673.30s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+673.30s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+673.45s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+678.21s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+678.21s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+678.38s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+683.62s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+683.62s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+683.77s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+694.40s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+694.40s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+694.55s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page [+700.26s] DEBUG: autosave-manager.vala:481: Found a page that needs to be recovered [+700.26s] DEBUG: autosave-manager.vala:497: Restoring a page of size 2549 x 4500 [+700.41s] DEBUG: autosave-manager.vala:528: Updating autosave to point to our new copy of the page and still going on until it recovers a previous scan, which I do not really need But I guess this issue is not impacting. I can launch a second simple- scan -d and kill the first one. Then I try to scan all pages in feeder, I get the following debugging log : simple-scan -d [+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.10.0, PID=11082 [+0.00s] DEBUG: Connecting to session manager [+0.75s] WARNING: g_object_set_valist: invalid object type 'GtkAdjustment' for value type 'GtkWidget' [+0.76s] DEBUG: ui.vala:1513: Restoring window to 600x400 pixels [+0.76s] DEBUG: ui.vala:1518: Restoring window to
[Bug 1266310] Re: impossible to scan all pages from feeder with HP OfficeJet 6310
Note : I got rid off the autosave.db, preventing first time simple-scan to launch quickly. I updated to simple-scan latest version. Simple Scan 3.11.3, released on 2013-12-18. Still experiencing same issue : impossible to scan multiple pages in a row via the scan all pages in feeder feature. log collected via simple-scan -d : simple-scan -d [+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.11.3, PID=22785 [+0.00s] DEBUG: Connecting to session manager [+0.06s] DEBUG: ui.vala:1638: Restoring window to 600x400 pixels [+0.06s] DEBUG: ui.vala:1643: Restoring window to maximized [+0.06s] DEBUG: autosave-manager.vala:64: Loading autosave information [+0.06s] DEBUG: autosave-manager.vala:258: Waiting to autosave... [+0.06s] WARNING: autosave-manager.vala:76: Could not load autosave infomation; not restoring any autosaves [+0.11s] DEBUG: scanner.vala:1443: sane_init () - SANE_STATUS_GOOD [+0.11s] DEBUG: scanner.vala:1449: SANE version 1.0.23 [+0.11s] DEBUG: scanner.vala:1510: Requesting redetection of scan devices [+0.11s] DEBUG: scanner.vala:802: Processing request [+0.24s] DEBUG: autosave-manager.vala:280: Autosaving book information [+2.81s] DEBUG: scanner.vala:338: sane_get_devices () - SANE_STATUS_GOOD [+2.81s] DEBUG: scanner.vala:350: Device: name=hpaio:/usb/Officejet_6300_series?serial=CN814FB1Y304J5 vendor=Hewlett-Packard model=Officejet_6300_series type=all-in-one [+21.11s] DEBUG: simple-scan.vala:310: Requesting scan at 300 dpi from device 'hpaio:/usb/Officejet_6300_series?serial=CN814FB1Y304J5' [+21.11s] DEBUG: scanner.vala:1556: Scanner.scan (hpaio:/usb/Officejet_6300_series?serial=CN814FB1Y304J5, dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=ScanType.ADF_BOTH, paper_width=0, paper_height=0, brightness=0, contrast=0) [+21.11s] DEBUG: scanner.vala:802: Processing request [+23.22s] DEBUG: scanner.vala:863: sane_open (hpaio:/usb/Officejet_6300_series?serial=CN814FB1Y304J5) - SANE_STATUS_GOOD [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (0) [+23.22s] DEBUG: scanner.vala:734: Option 0: title='Number of options' type=int size=4 cap=,soft-detect [+23.22s] DEBUG: scanner.vala:737: Description: Read-only option that specifies how many options a specific devices supports. [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (1) [+23.22s] DEBUG: scanner.vala:734: Option 1: name='(null)' title='Scan mode' type=group size=0 [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (2) [+23.22s] DEBUG: scanner.vala:734: Option 2: name='mode' title='Scan mode' type=string size=20 values=[Lineart, Gray, Color] cap=,soft-select,soft-detect [+23.22s] DEBUG: scanner.vala:737: Description: Selects the scan mode (e.g., lineart, monochrome, or color). [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (3) [+23.22s] DEBUG: scanner.vala:734: Option 3: name='resolution' title='Scan resolution' type=int size=4 unit=dpi values=[75, 100, 150, 200, 300, 600] cap=,soft-select,soft-detect [+23.22s] DEBUG: scanner.vala:737: Description: Sets the resolution of the scanned image. [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (4) [+23.22s] DEBUG: scanner.vala:734: Option 4: name='(null)' title='Advanced' type=group size=0 cap=,advanced [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (5) [+23.22s] DEBUG: scanner.vala:734: Option 5: name='contrast' title='Contrast' type=int size=4 min=-127, max=127, quant=0 cap=,soft-select,soft-detect,advanced [+23.22s] DEBUG: scanner.vala:737: Description: Controls the contrast of the acquired image. [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (6) [+23.22s] DEBUG: scanner.vala:734: Option 6: name='brightness' title='Brightness' type=int size=4 min=-127, max=127, quant=0 cap=,soft-select,soft-detect,advanced [+23.22s] DEBUG: scanner.vala:737: Description: Controls the brightness of the acquired image. [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (7) [+23.22s] DEBUG: scanner.vala:734: Option 7: name='compression' title='Compression' type=string size=20 values=[None, JPEG] cap=,soft-select,soft-detect,advanced [+23.22s] DEBUG: scanner.vala:737: Description: Selects the scanner compression method for faster scans, possibly at the expense of image quality. [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (8) [+23.22s] DEBUG: scanner.vala:734: Option 8: name='jpeg-quality' title='JPEG compression factor' type=int size=4 min=0, max=100, quant=0 cap=,soft-select,soft-detect,advanced [+23.22s] DEBUG: scanner.vala:737: Description: Sets the scanner JPEG compression factor. Larger numbers mean better compression, and smaller numbers mean better image quality. [+23.22s] DEBUG: scanner.vala:884: sane_get_option_descriptor (9) [+23.22s] DEBUG: scanner.vala:734: Option 9: name='batch-scan' title='Batch scan' type=bool size=4 cap=,soft-select,soft-detect,advanced [+23.22s] DEBUG: scanner.vala:737: Description: Enables continuous scanning
[Bug 1266310] Re: impossible to scan all pages from feeder with HP OfficeJet 6310
Thanks robert. I tested using your recommendation scanimage. $ scanimage test.pbm -- looks like scanning ok. However, to test the multipage feeder scanning, I used the following command : $ scanimage --batch test_batch.pbm Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 Scanned page 1. (scanner status = 5) Scanning page 2 Scanned page 2. (scanner status = 5) Scanning page 3 Scanned page 3. (scanner status = 5) Scanning page 4 Scanned page 4. (scanner status = 5) Scanning page 5 Scanned page 5. (scanner status = 5) Scanning page 6 Scanned page 6. (scanner status = 5) Scanning page 7 ^Cscanimage: received signal 2 scanimage: trying to stop scanner It scanned ok multiple pages. in both cases (single page or multipage), it outputs scanned image files so it is scanning ok both single pages or multiple pages via the feeder when using scanimage. What should we do now ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266310 Title: impossible to scan all pages from feeder with HP OfficeJet 6310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1266310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218196] Re: ASUS X54C. Key sequence Fn + F9 not working. Touchpad not responding.
I am experiencing the same problem. To be more precise, I can enable/disable my touchpad at will using `xinput set-prop` on the appropriate device or inserting/removing the kernel module `psmouse`. But anyhow, fn+f9 is the only special key shortcut which is not working. This is minor but quite disturbing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218196 Title: ASUS X54C. Key sequence Fn + F9 not working. Touchpad not responding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125678] [NEW] package redmine 1.4.4+dfsg1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: After not completing the configuration of MySQL, the installation of redmine seemingly wasn't rolled back when aborted. 1) I'm using Ubuntu 12.10. 2) I'm using redmine 1.4.4+dfsg1-1. 3) I expected redmine to remove the packages, scripts and configurations that were attempted installed before I began configuring MySQL. 4) Can't remember exactly, but some kind of error message, and an attempt to make me configure MySQL during my last distribution upgrade. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: redmine 1.4.4+dfsg1-1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 AptOrdering: steam: Install redmine: Configure steam: Configure Architecture: i386 Date: Fri Feb 15 00:28:21 2013 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2012-09-21 (146 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) MarkForUpload: True PackageArchitecture: all SourcePackage: redmine Title: package redmine 1.4.4+dfsg1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to quantal on 2013-01-16 (29 days ago) ** Affects: redmine (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125678 Title: package redmine 1.4.4+dfsg1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1125678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099903] Re: RMI Bug makes JVM Crash
** Summary changed: - RMI Bug make JVM Crash + RMI Bug makes JVM Crash ** Description changed: Using a 3rd application that connects to a tomcat serving using JMX to collect metrics make my tomcat server crash. Problem couldn't be reproduced when using Oracle JDK. + Tomcat version: 7.0 + Log file: http://keicheux.free.fr/hs_err_pid13639.log ** Description changed: - Using a 3rd application that connects to a tomcat serving using JMX to collect metrics make my tomcat server crash. + Using a 3rd party application that connects to a tomcat serving using JMX to collect metrics make my tomcat server crash. Problem couldn't be reproduced when using Oracle JDK. Tomcat version: 7.0 Log file: http://keicheux.free.fr/hs_err_pid13639.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099903 Title: RMI Bug makes JVM Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1099903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099903] [NEW] RMI Bug make JVM Crash
Public bug reported: Using a 3rd application that connects to a tomcat serving using JMX to collect metrics make my tomcat server crash. Problem couldn't be reproduced when using Oracle JDK. Log file: http://keicheux.free.fr/hs_err_pid13639.log ** Affects: openjdk-6 (Ubuntu) Importance: Undecided Status: New ** Tags: crash critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099903 Title: RMI Bug make JVM Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1099903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003419] [NEW] Lyx does not preserve DOS/Unix line endings
Public bug reported: I am working on a lyx document together with people that use Windows. Every time I save the document, all line endings get converted to \n (LF). Every time someone on Windows saves the document, all line endings get converted to \r\n (CR+LF). The document is versioned using SVN which now will show every line as changed in svn diff. This is unacceptable when merging changes from other people and I always have to use the tool unix2dos before committing, so that the diffs look reasonable. What I expected to happen: If opened document uses LF to end lines, save document using LF to end lines. If opened document uses CR+LF to end lines, save document using CR+LF to end lines. Like most text editors. What happened instead: LyX converts the line endings to the format native to the platform it is running on. LyX Version: This affects all versions prior to and including LyX 2.0.2. Ubuntu Version: Description:Ubuntu 12.04 LTS Release:12.04 ** Affects: lyx (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/1003419 Title: Lyx does not preserve DOS/Unix line endings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1003419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003419] Re: Lyx does not preserve DOS/Unix line endings
Thanks, that works for me. But I am not sure your argument holds. Firstly, IMO a .lyx file is a machine controlled file format which should probably not be edited by hand. At least that is what I think naive users should never do. But it is diff/merge friendly, except for the line endings. Secondly, _if_ a user is comfortable with opening and changing the file with text editors, I as a user expect the text editor to not change the line endings again. So LyX probably should not either. Thirdly, if I save the document now under Linux, my Windows users still have problems with Notepad. Conversely if LyX would preserve the line endings (or make it an option), then a document _created_ on Windows would choose CR+LF as default for this document. Therefore even when Linux users work with it, it would stay editable in Notepad. I would rate the current behaviour as worse than having a per document setting for line endings that defaults to the native line ending format. But you showed me a working solution, so I wont complain anymore :) Thank you for your time and your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003419 Title: Lyx does not preserve DOS/Unix line endings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1003419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993242] Re: 12.04 Alternate AMD64 freezes on language selection
I have the same problem. My system is an intel i7 on motherboard Gigabyte Z68X-UD3H-B3. The keyboard and mouse are both Logitech wireless. It freezes on the second language choice page with the cd ubuntu-12.04-alternate-amd64+mac. Thanks Remi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993242 Title: 12.04 Alternate AMD64 freezes on language selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/993242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog
Hi Frédéric, I got it working! Thank you very much! Rémi -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Wed, 21 Mar 2012 02:07:31 + Install VLC from the Software Center to have the picture. The list of channel is in the bottom of the window, you have to slide it to see the channel list (This is an other bug I have to fix). Cheers, Frederic On Tue, Mar 20, 2012 at 8:54 PM, Remi 951...@bugs.launchpad.net wrote: Hi Frédéric, I have tested the PPA available today. Follows the first sequence launched from the first terminal: remi@amazing:~$ me-tv-server 2012-03-20 20:18:01: Me TV Server 1.4.0.9 started 2012-03-20 20:18:01: An unhandled exception was generated 2012-03-20 20:18:01: Error: The Me TV database version does not match the Me TV server version. remi@amazing:~$ me-tv-client Me TV 1.4.0.9 2012-03-20 20:18:30: Me TV Server 1.4.0.9 started 2012-03-20 20:18:30: An unhandled exception was generated 2012-03-20 20:18:30: Error: The Me TV database version does not match the Me TV server version. 12-03-20 20:18:35: Exception: Failed to communicate with Me TV server remi@amazing:~$ rm ~/.local/share/me-tv/* rm: cannot remove `/home/remi/.local/share/me-tv/backups': Is a directory remi@amazing:~$ ls ~/.local/share/me-tv/ backups remi@amazing:~$ me-tv-server 2012-03-20 20:20:22: Me TV Server 1.4.0.9 started 2012-03-20 20:20:31: Device: 'Auvitek AU8522 QAM/8VSB Frontend' (ATSC) at /dev/dvb/adapter0/frontend0 2012-03-20 20:20:31: Starting socket service on port 1999 2012-03-20 20:20:31: Me TV Server entering main loop 2012-03-20 20:23:07: Frontend::tune_to(50900) 2012-03-20 20:23:07: Waiting for signal lock ... 2012-03-20 20:23:07: Got signal lock From that point I started a second terminal with the following: remi@amazing:~$ me-tv-client Me TV 1.4.0.9 Warning: option --alsa-caching no longer exists. Warning: option --udp-caching no longer exists. Warning: option --alsa-caching no longer exists. Warning: option --udp-caching no longer exists. libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) for PID 0 libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) for PID 255 [0x7fdc84000958] main video output error: video output creation failed [0x7fdca0008758] main decoder error: failed to create video output And from that point, the GUI pop-ups and I got the sound of a TV channel playing, but no image. I also can not change the TV channel I do not found a control to do it. Finally, it is a great improvement regarding the database bug. I will continue to test your next releases. Thank you. -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Tue, 20 Mar 2012 00:44:01 + Hi Rémi, Can you update again (you should receive 1.4.0.9 1.4.0-0~29~Precise1). I think I fix the bug with mismatch DB version. Thanks, Frederic On Sun, Mar 18, 2012 at 5:51 PM, Remi 951...@bugs.launchpad.net wrote: Hi Frédéric, I have tried 1.4.0.8 (in synaptic listed 1.4.0-0~27~precise1). I start first the server and then the client. The client was complaining the database version is not compatible with the server version. I have then killed both and erase /home/remi/.local/share/me-tv/me-tv.db and me-tv2.db. I try again, follows the outputs: remi@amazing:~$ me-tv-server 2012-03-18 16:56:57: Me TV Server 1.4.0.8 started From a second terminal: remi@amazing:~$ me-tv-client Me TV 1.4.0.8 2012-03-18 16:57:02: Me TV Server 1.4.0.8 started 2012-03-18 16:57:02: An unhandled exception was generated 2012-03-18 16:57:02: Error: The Me TV database version does not match the Me TV server version. 12-03-18 16:57:07: Exception: Failed to communicate with Me TV server remi@amazing:~$ A new database was generated as /home/remi/.local/share/me-tv/me-tv.db and I have included it as attachment. It seems it does not recognize the database that it have just generated. Follow the output following the second attempt to start the server: remi@amazing:~$ me-tv-server 2012-03-18 17:37:57: Me TV Server 1.4.0.8 started 2012-03-18 17:37:57: An unhandled exception was generated 2012-03-18 17:37:57: Error: The Me TV database version does not match the Me TV server version. remi@amazing:~$ I have then tried a last sequence: I erase the database, I stat the server (sucessfully), I erase again the database created by the sever, and start the client. The output follows: remi@amazing:~$ me-tv-client Me TV 1.4.0.8 2012-03-18 17:48:27: Me TV Server 1.4.0.8 started 12-03-18 17:48:32
Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog
Hi Frédéric, I have tested the PPA available today. Follows the first sequence launched from the first terminal: remi@amazing:~$ me-tv-server 2012-03-20 20:18:01: Me TV Server 1.4.0.9 started 2012-03-20 20:18:01: An unhandled exception was generated 2012-03-20 20:18:01: Error: The Me TV database version does not match the Me TV server version. remi@amazing:~$ me-tv-client Me TV 1.4.0.9 2012-03-20 20:18:30: Me TV Server 1.4.0.9 started 2012-03-20 20:18:30: An unhandled exception was generated 2012-03-20 20:18:30: Error: The Me TV database version does not match the Me TV server version. 12-03-20 20:18:35: Exception: Failed to communicate with Me TV server remi@amazing:~$ rm ~/.local/share/me-tv/* rm: cannot remove `/home/remi/.local/share/me-tv/backups': Is a directory remi@amazing:~$ ls ~/.local/share/me-tv/ backups remi@amazing:~$ me-tv-server 2012-03-20 20:20:22: Me TV Server 1.4.0.9 started 2012-03-20 20:20:31: Device: 'Auvitek AU8522 QAM/8VSB Frontend' (ATSC) at /dev/dvb/adapter0/frontend0 2012-03-20 20:20:31: Starting socket service on port 1999 2012-03-20 20:20:31: Me TV Server entering main loop 2012-03-20 20:23:07: Frontend::tune_to(50900) 2012-03-20 20:23:07: Waiting for signal lock ... 2012-03-20 20:23:07: Got signal lock From that point I started a second terminal with the following: remi@amazing:~$ me-tv-client Me TV 1.4.0.9 Warning: option --alsa-caching no longer exists. Warning: option --udp-caching no longer exists. Warning: option --alsa-caching no longer exists. Warning: option --udp-caching no longer exists. libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) for PID 0 libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) for PID 255 [0x7fdc84000958] main video output error: video output creation failed [0x7fdca0008758] main decoder error: failed to create video output And from that point, the GUI pop-ups and I got the sound of a TV channel playing, but no image. I also can not change the TV channel I do not found a control to do it. Finally, it is a great improvement regarding the database bug. I will continue to test your next releases. Thank you. -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Tue, 20 Mar 2012 00:44:01 + Hi Rémi, Can you update again (you should receive 1.4.0.9 1.4.0-0~29~Precise1). I think I fix the bug with mismatch DB version. Thanks, Frederic On Sun, Mar 18, 2012 at 5:51 PM, Remi 951...@bugs.launchpad.net wrote: Hi Frédéric, I have tried 1.4.0.8 (in synaptic listed 1.4.0-0~27~precise1). I start first the server and then the client. The client was complaining the database version is not compatible with the server version. I have then killed both and erase /home/remi/.local/share/me-tv/me-tv.db and me-tv2.db. I try again, follows the outputs: remi@amazing:~$ me-tv-server 2012-03-18 16:56:57: Me TV Server 1.4.0.8 started From a second terminal: remi@amazing:~$ me-tv-client Me TV 1.4.0.8 2012-03-18 16:57:02: Me TV Server 1.4.0.8 started 2012-03-18 16:57:02: An unhandled exception was generated 2012-03-18 16:57:02: Error: The Me TV database version does not match the Me TV server version. 12-03-18 16:57:07: Exception: Failed to communicate with Me TV server remi@amazing:~$ A new database was generated as /home/remi/.local/share/me-tv/me-tv.db and I have included it as attachment. It seems it does not recognize the database that it have just generated. Follow the output following the second attempt to start the server: remi@amazing:~$ me-tv-server 2012-03-18 17:37:57: Me TV Server 1.4.0.8 started 2012-03-18 17:37:57: An unhandled exception was generated 2012-03-18 17:37:57: Error: The Me TV database version does not match the Me TV server version. remi@amazing:~$ I have then tried a last sequence: I erase the database, I stat the server (sucessfully), I erase again the database created by the sever, and start the client. The output follows: remi@amazing:~$ me-tv-client Me TV 1.4.0.8 2012-03-18 17:48:27: Me TV Server 1.4.0.8 started 12-03-18 17:48:32: Exception: Failed to communicate with Me TV server remi@amazing:~$ Sorry for my late answer I was busy. Thanks a lot, Rémi -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Sun, 18 Mar 2012 15:25:14 + Hi Rémi, Can you try with the last version ? (1.4.0-0~27~Precise1). I think you already added the PPA for me-tv so you just have to update you system with update-manager or with these command: sudo apt-get update sudo apt-get upgrade Cheers, Frédéric ** Attachment added: me-tv.db https
Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog
Hi Frédéric, I have tried 1.4.0.8 (in synaptic listed 1.4.0-0~27~precise1). I start first the server and then the client. The client was complaining the database version is not compatible with the server version. I have then killed both and erase /home/remi/.local/share/me-tv/me-tv.db and me-tv2.db. I try again, follows the outputs: remi@amazing:~$ me-tv-server 2012-03-18 16:56:57: Me TV Server 1.4.0.8 started From a second terminal: remi@amazing:~$ me-tv-client Me TV 1.4.0.8 2012-03-18 16:57:02: Me TV Server 1.4.0.8 started 2012-03-18 16:57:02: An unhandled exception was generated 2012-03-18 16:57:02: Error: The Me TV database version does not match the Me TV server version. 12-03-18 16:57:07: Exception: Failed to communicate with Me TV server remi@amazing:~$ A new database was generated as /home/remi/.local/share/me-tv/me-tv.db and I have included it as attachment. It seems it does not recognize the database that it have just generated. Follow the output following the second attempt to start the server: remi@amazing:~$ me-tv-server 2012-03-18 17:37:57: Me TV Server 1.4.0.8 started 2012-03-18 17:37:57: An unhandled exception was generated 2012-03-18 17:37:57: Error: The Me TV database version does not match the Me TV server version. remi@amazing:~$ I have then tried a last sequence: I erase the database, I stat the server (sucessfully), I erase again the database created by the sever, and start the client. The output follows: remi@amazing:~$ me-tv-client Me TV 1.4.0.8 2012-03-18 17:48:27: Me TV Server 1.4.0.8 started 12-03-18 17:48:32: Exception: Failed to communicate with Me TV server remi@amazing:~$ Sorry for my late answer I was busy. Thanks a lot, Rémi -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Sun, 18 Mar 2012 15:25:14 + Hi Rémi, Can you try with the last version ? (1.4.0-0~27~Precise1). I think you already added the PPA for me-tv so you just have to update you system with update-manager or with these command: sudo apt-get update sudo apt-get upgrade Cheers, Frédéric ** Attachment added: me-tv.db https://bugs.launchpad.net/bugs/951720/+attachment/2894278/+files/me-tv.db -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951720 Title: me-tv freezes when clicking OK on the Channels Editor dialog To manage notifications about this bug go to: https://bugs.launchpad.net/me-tv/+bug/951720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog
Hi Frédéric, I will continue to follow the ppa updates and provide you with my feedback. What about the impact on the next Ubuntu 12.04 release? Thanks a lot, Rémi -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Sun, 11 Mar 2012 22:27:44 + Hi Remi, The mismatch me-tv database is next in my to-do list. I will begin the work of understanding what happen (or not) in the next week. Cheers, Frederic On Sun, Mar 11, 2012 at 1:38 PM, Remi 951...@bugs.launchpad.net wrote: Hi Frederic, Thanks for your reply. I have added the ppa and installed the version 1.4.0-0~18~precise1 from Synaptic, but I got the Bug#886367. Regarding the bug with versions 1.2.6 and 1.3.6, I suspect the origin is more specific to Ubuntu 12.04 Beta 1 64 bit than from me-tv. Rémi -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Sun, 11 Mar 2012 01:54:51 + Hi Remi, You can also try with version 1.4.0. The easiest way to do it is via the PPA: https://launchpad.net/~me-tv-development/+archive/ppa Cheers, Frederic On Sat, Mar 10, 2012 at 1:39 PM, Remi 951...@bugs.launchpad.net wrote: -- You received this bug notification because you are a member of Me TV Development, which is subscribed to me-tv in Ubuntu. https://bugs.launchpad.net/bugs/951720 Title: me-tv freezes when clicking OK on the Channels Editor dialog Status in “me-tv” package in Ubuntu: New Bug description: After importing my channels successfuly from my channels.conf file, when I click OK on the Channel Editor window, me-tv freezes definitively using 0% CPU. I got the bug with the version 1.3.6 installed from software center in ubuntu 12.04 Beta 1. I also uninstall me-tv and compile version 1.2.6. I got the exact same bug. System: Ubuntu 12.04 Beta 1 Gigabyte Z68X-UD3H-B3 i7-3600K 12 Gb RAM Tuner Hauppauge WinTV-HVR 950q Follows the output from command line for v 1.3.6: remi@amazing:/usr/share$ /usr/bin/me-tv -v Me TV 1.3.6 12-03-10 13:32:44: Application constructor 12-03-10 13:32:44: sqlite3_threadsafe() = 1 12-03-10 13:32:44: Database 'exists' 12-03-10 13:32:44: Opening database file '/home/remi/.local/share/me-tv/me-tv.db' 12-03-10 13:32:44: Loading UI files 12-03-10 13:32:44: Application constructed 12-03-10 13:32:44: Initialising table 'version' 12-03-10 13:32:44: Required Database version: 6 12-03-10 13:32:44: Actual Database version: 6 12-03-10 13:32:44: Me TV database initialised 12-03-10 13:32:44: StatusIcon constructor started 12-03-10 13:32:44: StatusIcon constructed 12-03-10 13:32:44: MainWindow constructor 12-03-10 13:32:44: MainWindow constructed 12-03-10 13:32:44: Scanning DVB devices ... 12-03-10 13:32:44: Opening frontend device: /dev/dvb/adapter0/frontend0 12-03-10 13:32:51: Device: 'Auvitek AU8522 QAM/8VSB Frontend' (ATSC) at /dev/dvb/adapter0/frontend0 12-03-10 13:32:51: Loading channels ... 12-03-10 13:32:51: Channels loaded 12-03-10 13:32:51: Creating stream manager 12-03-10 13:32:51: Creating frontend thread 12-03-10 13:32:51: Thread 'Frontend' created 12-03-10 13:32:51: Creating FrontendThread (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Opening frontend device '/dev/dvb/adapter0/dvr0' for reading ... 12-03-10 13:32:51: FrontendThread created (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Starting frontend thread 12-03-10 13:32:51: Starting frontend thread (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Waiting for 'Frontend' to start 12-03-10 13:32:51: Frontend thread running (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Entering FrontendThread loop (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Thread 'Frontend' started 12-03-10 13:32:51: Loading scheduled recordings 12-03-10 13:32:51: Scheduled recordings loaded 12-03-10 13:32:51: Setting geometry (3, 211, 781, 656) 12-03-10 13:32:51: No channels, nothing to play 12-03-10 13:32:51: Checking '/usr/share/dvb' 12-03-10 13:32:51: Found '/usr/share/dvb/atsc' 12-03-10 13:32:51: Updating EPG 12-03-10 13:32:51: EPG update complete 12-03-10 13:33:15: Line 1 (6 parameters): 'Radio-Canada:20700:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : Radio-Canada 12-03-10 13:33:15: Line 2 (6 parameters): 'Tele-Quebec:47900:VSB_8:49:53:3 ' 12-03-10 13:33:15: Added channel 3 : Tele-Quebec 12-03-10 13:33:15: Line 3 (6 parameters): 'CFCM-HD:49100:VSB_8:49:52:1 ' 12-03-10 13:33:15: Added channel 1 : CFCM-HD 12-03-10 13:33:15
Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog
Hi Frederic, Thanks for your reply. I have added the ppa and installed the version 1.4.0-0~18~precise1 from Synaptic, but I got the Bug#886367. Regarding the bug with versions 1.2.6 and 1.3.6, I suspect the origin is more specific to Ubuntu 12.04 Beta 1 64 bit than from me-tv. Rémi -Original Message- From: Frédéric Côté 951...@bugs.launchpad.net Reply-to: Bug 951720 951...@bugs.launchpad.net To: remi.dem...@videotron.ca Subject: Re: [Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog Date: Sun, 11 Mar 2012 01:54:51 + Hi Remi, You can also try with version 1.4.0. The easiest way to do it is via the PPA: https://launchpad.net/~me-tv-development/+archive/ppa Cheers, Frederic On Sat, Mar 10, 2012 at 1:39 PM, Remi 951...@bugs.launchpad.net wrote: -- You received this bug notification because you are a member of Me TV Development, which is subscribed to me-tv in Ubuntu. https://bugs.launchpad.net/bugs/951720 Title: me-tv freezes when clicking OK on the Channels Editor dialog Status in “me-tv” package in Ubuntu: New Bug description: After importing my channels successfuly from my channels.conf file, when I click OK on the Channel Editor window, me-tv freezes definitively using 0% CPU. I got the bug with the version 1.3.6 installed from software center in ubuntu 12.04 Beta 1. I also uninstall me-tv and compile version 1.2.6. I got the exact same bug. System: Ubuntu 12.04 Beta 1 Gigabyte Z68X-UD3H-B3 i7-3600K 12 Gb RAM Tuner Hauppauge WinTV-HVR 950q Follows the output from command line for v 1.3.6: remi@amazing:/usr/share$ /usr/bin/me-tv -v Me TV 1.3.6 12-03-10 13:32:44: Application constructor 12-03-10 13:32:44: sqlite3_threadsafe() = 1 12-03-10 13:32:44: Database 'exists' 12-03-10 13:32:44: Opening database file '/home/remi/.local/share/me-tv/me-tv.db' 12-03-10 13:32:44: Loading UI files 12-03-10 13:32:44: Application constructed 12-03-10 13:32:44: Initialising table 'version' 12-03-10 13:32:44: Required Database version: 6 12-03-10 13:32:44: Actual Database version: 6 12-03-10 13:32:44: Me TV database initialised 12-03-10 13:32:44: StatusIcon constructor started 12-03-10 13:32:44: StatusIcon constructed 12-03-10 13:32:44: MainWindow constructor 12-03-10 13:32:44: MainWindow constructed 12-03-10 13:32:44: Scanning DVB devices ... 12-03-10 13:32:44: Opening frontend device: /dev/dvb/adapter0/frontend0 12-03-10 13:32:51: Device: 'Auvitek AU8522 QAM/8VSB Frontend' (ATSC) at /dev/dvb/adapter0/frontend0 12-03-10 13:32:51: Loading channels ... 12-03-10 13:32:51: Channels loaded 12-03-10 13:32:51: Creating stream manager 12-03-10 13:32:51: Creating frontend thread 12-03-10 13:32:51: Thread 'Frontend' created 12-03-10 13:32:51: Creating FrontendThread (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Opening frontend device '/dev/dvb/adapter0/dvr0' for reading ... 12-03-10 13:32:51: FrontendThread created (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Starting frontend thread 12-03-10 13:32:51: Starting frontend thread (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Waiting for 'Frontend' to start 12-03-10 13:32:51: Frontend thread running (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Entering FrontendThread loop (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Thread 'Frontend' started 12-03-10 13:32:51: Loading scheduled recordings 12-03-10 13:32:51: Scheduled recordings loaded 12-03-10 13:32:51: Setting geometry (3, 211, 781, 656) 12-03-10 13:32:51: No channels, nothing to play 12-03-10 13:32:51: Checking '/usr/share/dvb' 12-03-10 13:32:51: Found '/usr/share/dvb/atsc' 12-03-10 13:32:51: Updating EPG 12-03-10 13:32:51: EPG update complete 12-03-10 13:33:15: Line 1 (6 parameters): 'Radio-Canada:20700:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : Radio-Canada 12-03-10 13:33:15: Line 2 (6 parameters): 'Tele-Quebec:47900:VSB_8:49:53:3 ' 12-03-10 13:33:15: Added channel 3 : Tele-Quebec 12-03-10 13:33:15: Line 3 (6 parameters): 'CFCM-HD:49100:VSB_8:49:52:1 ' 12-03-10 13:33:15: Added channel 1 : CFCM-HD 12-03-10 13:33:15: Line 4 (6 parameters): 'CKMI-HD:50900:VSB_8:49:52:1 ' 12-03-10 13:33:15: Added channel 1 : CKMI-HD 12-03-10 13:33:15: Line 5 (6 parameters): 'CKMI-SD:50900:VSB_8:65:68:2 ' 12-03-10 13:33:15: Added channel 2 : CKMI-SD 12-03-10 13:33:15: Line 6 (6 parameters): 'CBVT-DT:53900:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : CBVT-DT 12-03-10 13:33:15: Line 7 (6 parameters): 'CFAP-DT:62300:VSB_8:49:51:1 ' 12-03-10 13:33:15: Added channel 1 : CFAP-DT 12-03-10 13:33:15: Line 8 (6 parameters): 'CIVC-HD:65900:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : CIVC-HD 12-03-10 13:33:15: Line 9 (1 parameters): ' ' 12-03-10 13:33:15: Finished importing channels 12-03-10 13:33:39: Stopping frontend thread 12-03-10 13:33:39: Stopping
[Bug 951427] [NEW] Intel GMA 3150 not working on N550 CPU
Public bug reported: I have installed Ubuntu with use of Wubi, there is no support for Intel GMA 3150 chipset as found in the Atom N550 CPU. As a result my system underperforms. (And my system is not fast as it is) As I am new to Linux (my ANDROID phone the first ever Linux I played with) I cannot go install custom Kernels or someting. I understand it does not work with a driver. So my only hope is it gets fixed for me in an update!! The Intel Atom is a very common CPU for netbooks so GMA 3150 should work on Ubuntu, but it does not. There is support from Intel, but it involves building kernels. I'm just a beginner wanting the Video Chipset to work, to get te full potential of Ubuntu. Good thing is, al my other hardware works fine! But the display driver is the most important one!! I think is classiefies a bug, te reproduce Install Ubuntu on a N550 or N570 netbook. Hope it gets fixed soon! I am very impressed with how far Ubuntu is compered with Windows. Remi van Dongen ** 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/951427 Title: Intel GMA 3150 not working on N550 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/951427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951720] Re: me-tv freezes when clicking OK on the Channels Editor dialog
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951720 Title: me-tv freezes when clicking OK on the Channels Editor dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/me-tv/+bug/951720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951720] [NEW] me-tv freezes when clicking OK on the Channels Editor dialog
Public bug reported: After importing my channels successfuly from my channels.conf file, when I click OK on the Channel Editor window, me-tv freezes definitively using 0% CPU. I got the bug with the version 1.3.6 installed from software center in ubuntu 12.04 Beta 1. I also uninstall me-tv and compile version 1.2.6. I got the exact same bug. System: Ubuntu 12.04 Beta 1 Gigabyte Z68X-UD3H-B3 i7-3600K 12 Gb RAM Tuner Hauppauge WinTV-HVR 950q Follows the output from command line for v 1.3.6: remi@amazing:/usr/share$ /usr/bin/me-tv -v Me TV 1.3.6 12-03-10 13:32:44: Application constructor 12-03-10 13:32:44: sqlite3_threadsafe() = 1 12-03-10 13:32:44: Database 'exists' 12-03-10 13:32:44: Opening database file '/home/remi/.local/share/me-tv/me-tv.db' 12-03-10 13:32:44: Loading UI files 12-03-10 13:32:44: Application constructed 12-03-10 13:32:44: Initialising table 'version' 12-03-10 13:32:44: Required Database version: 6 12-03-10 13:32:44: Actual Database version: 6 12-03-10 13:32:44: Me TV database initialised 12-03-10 13:32:44: StatusIcon constructor started 12-03-10 13:32:44: StatusIcon constructed 12-03-10 13:32:44: MainWindow constructor 12-03-10 13:32:44: MainWindow constructed 12-03-10 13:32:44: Scanning DVB devices ... 12-03-10 13:32:44: Opening frontend device: /dev/dvb/adapter0/frontend0 12-03-10 13:32:51: Device: 'Auvitek AU8522 QAM/8VSB Frontend' (ATSC) at /dev/dvb/adapter0/frontend0 12-03-10 13:32:51: Loading channels ... 12-03-10 13:32:51: Channels loaded 12-03-10 13:32:51: Creating stream manager 12-03-10 13:32:51: Creating frontend thread 12-03-10 13:32:51: Thread 'Frontend' created 12-03-10 13:32:51: Creating FrontendThread (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Opening frontend device '/dev/dvb/adapter0/dvr0' for reading ... 12-03-10 13:32:51: FrontendThread created (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Starting frontend thread 12-03-10 13:32:51: Starting frontend thread (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Waiting for 'Frontend' to start 12-03-10 13:32:51: Frontend thread running (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Entering FrontendThread loop (/dev/dvb/adapter0/frontend0) 12-03-10 13:32:51: Thread 'Frontend' started 12-03-10 13:32:51: Loading scheduled recordings 12-03-10 13:32:51: Scheduled recordings loaded 12-03-10 13:32:51: Setting geometry (3, 211, 781, 656) 12-03-10 13:32:51: No channels, nothing to play 12-03-10 13:32:51: Checking '/usr/share/dvb' 12-03-10 13:32:51: Found '/usr/share/dvb/atsc' 12-03-10 13:32:51: Updating EPG 12-03-10 13:32:51: EPG update complete 12-03-10 13:33:15: Line 1 (6 parameters): 'Radio-Canada:20700:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : Radio-Canada 12-03-10 13:33:15: Line 2 (6 parameters): 'Tele-Quebec:47900:VSB_8:49:53:3 ' 12-03-10 13:33:15: Added channel 3 : Tele-Quebec 12-03-10 13:33:15: Line 3 (6 parameters): 'CFCM-HD:49100:VSB_8:49:52:1 ' 12-03-10 13:33:15: Added channel 1 : CFCM-HD 12-03-10 13:33:15: Line 4 (6 parameters): 'CKMI-HD:50900:VSB_8:49:52:1 ' 12-03-10 13:33:15: Added channel 1 : CKMI-HD 12-03-10 13:33:15: Line 5 (6 parameters): 'CKMI-SD:50900:VSB_8:65:68:2 ' 12-03-10 13:33:15: Added channel 2 : CKMI-SD 12-03-10 13:33:15: Line 6 (6 parameters): 'CBVT-DT:53900:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : CBVT-DT 12-03-10 13:33:15: Line 7 (6 parameters): 'CFAP-DT:62300:VSB_8:49:51:1 ' 12-03-10 13:33:15: Added channel 1 : CFAP-DT 12-03-10 13:33:15: Line 8 (6 parameters): 'CIVC-HD:65900:VSB_8:49:52:3 ' 12-03-10 13:33:15: Added channel 3 : CIVC-HD 12-03-10 13:33:15: Line 9 (1 parameters): ' ' 12-03-10 13:33:15: Finished importing channels 12-03-10 13:33:39: Stopping frontend thread 12-03-10 13:33:39: Stopping frontend thread (/dev/dvb/adapter0/frontend0) 12-03-10 13:33:39: Thread 'Frontend' marked for termination 12-03-10 13:33:39: Thread 'Frontend' waiting for join ... 12-03-10 13:33:39: FrontendThread loop exited (/dev/dvb/adapter0/frontend0) 12-03-10 13:33:39: Thread 'Frontend' exited 12-03-10 13:33:39: Thread 'Frontend' joined 12-03-10 13:33:39: Frontend thread stopped and joined (/dev/dvb/adapter0/frontend0) 12-03-10 13:33:39: Setting channels 12-03-10 13:33:39: Channels cleared 12-03-10 13:33:39: Channel 'Radio-Canada' added 12-03-10 13:33:39: Channel 'Tele-Quebec' added 12-03-10 13:33:39: Channel 'CFCM-HD' added 12-03-10 13:33:39: Channel 'CKMI-HD' added 12-03-10 13:33:39: Channel 'CKMI-SD' added 12-03-10 13:33:39: Channel 'CBVT-DT' added 12-03-10 13:33:39: Channel 'CFAP-DT' added 12-03-10 13:33:39: Channel 'CIVC-HD' added 12-03-10 13:33:39: Saving channels 12-03-10 13:33:39: Saving channel 'Radio-Canada' 12-03-10 13:33:39: Channel 'Radio-Canada' saved 12-03-10 13:33:39: Saving channel 'Tele-Quebec' 12-03-10 13:33:39: Channel 'Tele-Quebec' saved 12-03-10 13:33:39: Saving channel 'CFCM-HD' 12-03-10 13:33:39: Channel 'CFCM-HD' saved 12-03-10 13:33:39: Saving channel 'CKMI-HD' 12-03-10 13:33:39: Channel 'CKMI-HD' saved 12-03-10 13
[Bug 950045] [NEW] Dutch locale settings date format not correct
Public bug reported: Hi, I installed Ubunt via Windows wubi, I installed all updates. I set language to US International. Then I have also downloaded Dutch language. And only set currency and date format to Dutch. (I prefer English with Dutch date and time settings) The date format for Dutch is not correct, visible in the dateformat screen. If you apply this uncorrect date-format systemwide Ubuntu will not boot anymore. I'm now forced to use US date and currency format. For the one that fixes this: Date format: 31-12-2012 Currency: [Euro sign] 1,95 (1 Euro 95) Numbers 1.00.000,5 (One Hundered Thousend and 1 half) Well, I don't know if it count as security vulnerability, but I'm sure people that find Ubuntu not booting after half a day of updates will be unhappy. (Re-installed ubuntu 4x before I found the probable cause) Kindest regards, Remi van Dongen ** 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/950045 Title: Dutch locale settings date format not correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/950045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875538] Re: [Firefox 3.6.23] Impossible to open firefox because firefox-bin process is still running
problem occurs when you shut down the computer with Firefox still running. Simple solution is to delete the lock and .parantlock files from: //personal folder/.mozilla/firefox/(insert).default and firefox will run just fine again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875538 Title: [Firefox 3.6.23] Impossible to open firefox because firefox-bin process is still running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/875538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875538] Re: [Firefox 3.6.23] Impossible to open firefox because firefox-bin process is still running
I've got 10.10.10 over here and also since I upgraded to 3.6.23 I got exactly the same issue. When I tried to shut down, a message box prompted me that firefox-bin wasn't shut down proparly and I had to kill the process or force a shut down. Also when I closed Firefox and I tried to start it again it prompted that Firefox was already running. The lock file seen to be a hyper link to an non existing target (broken). After I've deleted this and the .parentlock file, Firefox did close down properly again and could start it as normal after I've closed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875538 Title: [Firefox 3.6.23] Impossible to open firefox because firefox-bin process is still running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/875538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259219] Re: Broken TLS support in libGL.so AKA: software-center crashed with SIGSEGV in __cxa_allocate_exception()
Never mind sudo apt-get update sudo apt-get upgrade did work for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/259219 Title: Broken TLS support in libGL.so AKA: software-center crashed with SIGSEGV in __cxa_allocate_exception() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259219] Re: Broken TLS support in libGL.so AKA: software-center crashed with SIGSEGV in __cxa_allocate_exception()
Updating does not fixes this here, Maverick meerkat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/259219 Title: Broken TLS support in libGL.so AKA: software-center crashed with SIGSEGV in __cxa_allocate_exception() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768586] [NEW] package grub-pc 1.99~rc1-13ubuntu3 failed to install
Public bug reported: Binary package hint: grub2 Error while upgrading. No more info, sorry :( ProblemType: Package DistroRelease: Ubuntu 11.04 Package: grub-pc 1.99~rc1-13ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Apr 21 22:03:10 2011 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413) ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-2.6.38-8-generic root=UUID=3292b06a-e788-43c7-9925-4acb60725f55 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: grub2 Title: package grub-pc 1.99~rc1-13ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to natty on 2011-04-21 (0 days ago) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768586 Title: package grub-pc 1.99~rc1-13ubuntu3 failed to install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768586] Re: package grub-pc 1.99~rc1-13ubuntu3 failed to install
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768586 Title: package grub-pc 1.99~rc1-13ubuntu3 failed to install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 743210] [NEW] package linux-image-2.6.32-29-generic 2.6.32-29.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: comment faire pour gagner de l espace disque ProblemType: Package DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-29-generic 2.6.32-29.58 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Mar 26 17:42:49 2011 DpkgTerminalLog: Log started: 2011-03-26 17:39:22 ErrorMessage: subprocess installed post-installation script returned error exit status 2 SourcePackage: linux Title: package linux-image-2.6.32-29-generic 2.6.32-29.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743210 Title: package linux-image-2.6.32-29-generic 2.6.32-29.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 743210] Re: package linux-image-2.6.32-29-generic 2.6.32-29.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743210 Title: package linux-image-2.6.32-29-generic 2.6.32-29.58 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515154] Re: Sound freeze when changing volume since Ubuntu 9.10
The problem does not affect the use of alsamixer to change volume, so I don't think the problem is directly with alsa, but rather, how pulseaudio is interacting with alsa with this driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/515154 Title: Sound freeze when changing volume since Ubuntu 9.10 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515154] Re: Sound freeze when changing volume since Ubuntu 9.10
I was even more confused than usual.. Please disregard above comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/515154 Title: Sound freeze when changing volume since Ubuntu 9.10 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663069] Re: non-accessable symlink errors when using aufs-shaddowed read-only root filesystem
Can be easily reproduced with the following steps:
mkdir ro rw aufs
touch ro/foo
sudo mount -t aufs -o br:rw:ro none aufs
mv aufs/{foo,bar}
Gives the following output:
mv: cannot move `aufs/foo' to `aufs/bar': Operation not permitted
And:
dmesg | tail -1
[179473.298795] non-accessible hardlink creation was attempted by: mv (fsuid
1000)
I confirm the kernel.yama.protected_nonaccess_hardlinks=0 workaround
--
non-accessable symlink errors when using aufs-shaddowed read-only root
filesystem
https://bugs.launchpad.net/bugs/663069
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 638709] Re: the thin 1px window border makes really hard to resize windows
*** This bug is a duplicate of bug 160311 *** https://bugs.launchpad.net/bugs/160311 This 'bug' should not be marked a dupe of 160311. It would be nice if metacity and compiz somehow invented a completely new, intuitive method to resize windows that any user somewhat familiar with common gui's used the past 10 years or so could immediately grasp without having to google.. In the real world however, that job is done by window borders. Releasing a default theme for what should be the friendliest desktop linux system that turns window resizing into an exercise in mouse dexterity is truly mind boggling. -- the thin 1px window border makes really hard to resize windows https://bugs.launchpad.net/bugs/638709 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 652393] Re: Nautilus can't display properties of mkv file with flac audio
Bug is fixed in Maverick. -- Nautilus can't display properties of mkv file with flac audio https://bugs.launchpad.net/bugs/652393 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 540820] Re: Thunderbird 3 TreeView selected color is hard to read
I think this bug should be moved to the Thunderbird package (not that
you can get upstream to fix anything they broke from 2.x to 3.x). There
are several themes and colors this new feature will mis-behave with.
A work around is to create a chome/userChrome.css file in your
Thunderbird profile directory and add this code:
treechildren::-moz-tree-cell-text(folderNameCol, newMessages-true) {
font-weight: bold;
color: #00 !important;
}
Note that color: #00 is black,,, modify to your taste.
--
Thunderbird 3 TreeView selected color is hard to read
https://bugs.launchpad.net/bugs/540820
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 388127] Re: please upgrade to version 0.5 - it already works with dpkg install
version is now 0.5.2 on lucid. I, am closing this bug ** Changed in: xmoto (Ubuntu) Status: New = Fix Released -- please upgrade to version 0.5 - it already works with dpkg install https://bugs.launchpad.net/bugs/388127 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 655469] [NEW] gnome-mplayer can not use embedded fonts
Public bug reported: Binary package hint: gnome-mplayer Gnome-mplayer always adds the -noembeddedfonts option to mplayer, regardless of whether or not the check mark in options to use embedded fonts is on or off. As a result, gnome-mplayer can not properly play files with subtitles that rely on embedded fonts, even though mplayer and smplayer can. I tried to work around by appending -embeddedfonts to the gnome options, but that didn't work. It seems the -noembeddedfonts hard coded from gnome-mplayer takes precedence. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-mplayer (not installed) ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Tue Oct 5 23:22:16 2010 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: gnome-mplayer ** Affects: gnome-mplayer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- gnome-mplayer can not use embedded fonts https://bugs.launchpad.net/bugs/655469 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 649457] Re: Sound volume control doesn't work on network sound server
Thanks for taking the time to look into this... Wherever the 'feature' originates, I have to reiterate that of the 3 gui volume control apps I have installed by default, Sound Properties, Gnome-volume-control applet and Sound Indicator, Sound indicator is the only one that doesn't follow along. -- Sound volume control doesn't work on network sound server https://bugs.launchpad.net/bugs/649457 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 654738] [NEW] Changing themes overwrites backgrounds.xml
Public bug reported: Binary package hint: gnome-control-center When user changes theme in the Gnome-appearance application, the .gnome2/backgrounds.xml file gets overwritten with an empty blank file, preventing the user from quickly switching to pre-defined favorite desktop backgrounds. Expected behaviour: Changing the theme should not affect backgrounds.xml ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-control-center 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Mon Oct 4 14:06:54 2010 ExecutablePath: /usr/bin/gnome-appearance-properties InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: gnome-control-center ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Changing themes overwrites backgrounds.xml https://bugs.launchpad.net/bugs/654738 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 654738] Re: Changing themes overwrites backgrounds.xml
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/654738/+attachment/1671767/+files/Dependencies.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/654738/+attachment/1671768/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/654738/+attachment/1671769/+files/ProcStatus.txt ** Attachment added: XsessionErrors.txt https://bugs.launchpad.net/bugs/654738/+attachment/1671770/+files/XsessionErrors.txt -- Changing themes overwrites backgrounds.xml https://bugs.launchpad.net/bugs/654738 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 615382] Re: burning fails to reload tray
As a work around to this problem, invoke growisofs with the notray option. Example: growisofs -use-the-force-luke=notray -Z /dev/dvd=myiso.iso Someone might want to patch growisofs so this is default, as the old re- load media behavior does not seem to be needed with current kernels or udev, or whatever. Something is pro-actively resetting the DVD drive as soon as the burn is complete. -- burning fails to reload tray https://bugs.launchpad.net/bugs/615382 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 652393] Re: Nautilus can't display properties of mkv file with flac audio
I've created and attached a video file that demonstrates the problem. ** Attachment added: sample_flac.mkv https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/652393/+attachment/1663506/+files/sample_flac.mkv -- Nautilus can't display properties of mkv file with flac audio https://bugs.launchpad.net/bugs/652393 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 652393] Re: Nautilus can't display properties of mkv file with flac audio
Embarrassingly, that sample does not actually trigger the bug I was reporting. A mod can please feel free to delete the 10MB waste of space, while I go back to the drawing board to figure out what combination exactly can reproduce it. Unfortunately, the only files I have that can reliably cause this problem are hundreds of MB. If a dev wants to look into this but needs a sample, please let me know and I can provide a high speed download link for one. -- Nautilus can't display properties of mkv file with flac audio https://bugs.launchpad.net/bugs/652393 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 652393] Re: Nautilus can't display properties of mkv file with flac audio
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/652393/+attachment/1659345/+files/Dependencies.txt ** Attachment added: usr_lib_nautilus.txt https://bugs.launchpad.net/bugs/652393/+attachment/1659346/+files/usr_lib_nautilus.txt -- Nautilus can't display properties of mkv file with flac audio https://bugs.launchpad.net/bugs/652393 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 652393] [NEW] Nautilus can't display properties of mkv file with flac audio
Public bug reported: Binary package hint: nautilus This bug applies to mkv files with h264 video and flac audio. Restricted Extras package is installed. Rick click on file and Select Properties, but properties windos never appears. Dialogue box pops up Creating Properties Window You can stop this operation by clicking Cancel..but the properties window is never successfully created. I believe this bug might actually reside with Gstreamer, sinceit seems in Lucid, no Gstreamer app Ive tried so far is actually able to play or even identify Flac audio in mkv files. However, it's also troublesome that I can't not do anything with the files in Nautilus, even if the media detection isn't working as it shout. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Thu Sep 30 16:17:47 2010 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Nautilus can't display properties of mkv file with flac audio https://bugs.launchpad.net/bugs/652393 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 649457] [NEW] Sound volume control doesn't work on network sound server
Public bug reported: Binary package hint: indicator-sound From Lucid, version 0.2.2-0ubuntu1 When sound is directed to another computer with Pulse Device Chooser applet, the indicator sound volume control does not work.. However, opening the sound preferences and using the volume slider there does work perfectly. (For added insult, using the old and much loved gnome volume control applet also works in this scenario.) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- Sound volume control doesn't work on network sound server https://bugs.launchpad.net/bugs/649457 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 636280] Re: Missing Redshift PPA for Maverick / Wrong default packages' sources
No those PPAs are not installed by default. You might have used the redshift repos before upgrading to maverick. When you upgrades your computer to a new version it browses all your subribed PPAS and replace the ubuntu version name. In this case it moves your PPAS form Jaunty to Maverick. To me this is not a bug, I ll change the bug status to invalid. Regards ** Changed in: update-manager (Ubuntu) Status: New = Invalid -- Missing Redshift PPA for Maverick / Wrong default packages' sources https://bugs.launchpad.net/bugs/636280 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 644620] Re: unison does not sync
Hi, What is your configuration and where are located the two folders you are trying to sync ? It looks you are trying to sync two folders : one on maveric running unisson 2.32 to another computer running karmic with unisson 2.27. the documentations says you MUST use the same version on the two computers. Please see: http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable /unison-manual.html#rshmeth Regards Remi ** Changed in: unison (Ubuntu) Status: New = Incomplete -- unison does not sync https://bugs.launchpad.net/bugs/644620 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 311803] Re: [Jaunty] banshee does not save window position when minimized to tray
It affects me on Lucid with version installed : banshee_1.6.1-1~lucid1_i386.deb -- [Jaunty] banshee does not save window position when minimized to tray https://bugs.launchpad.net/bugs/311803 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 603971] Re: previous button must be pressed several times to go the previous song
It looks there is on maverick a 4seconds delay before swithching between previous to repeat. Could anyone confirm ? -- previous button must be pressed several times to go the previous song https://bugs.launchpad.net/bugs/603971 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 581278] Re: rating to currently played song ignored
Do you still have the problem ? It looks to work perfectly on 1.6.1 ** Changed in: banshee (Ubuntu) Status: New = Incomplete -- rating to currently played song ignored https://bugs.launchpad.net/bugs/581278 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 616884] [NEW] kpackagekit makes apt-get upgrade fail while running
Public bug reported: Binary package hint: kpackagekit I run a apt-get update on kubuntu maverick and then a apt-get dist- upgrade with a lots of package to upgrade. while this was running i openned kpackagekit and then runned a second update. Both crashed. The apt-get dist-upgrade tell me the datas are in use by another process. Kpackagekit tells me there 's no cache for data and package needs to be rebuilt. ** Affects: kpackagekit (Ubuntu) Importance: Undecided Status: New -- kpackagekit makes apt-get upgrade fail while running https://bugs.launchpad.net/bugs/616884 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 590971] Re: acgvision-agent: package description formating issues
** Changed in: acgvision-agent Status: Fix Committed = Fix Released ** Changed in: acgvision-agent (Ubuntu) Assignee: (unassigned) = Remi Debay (debay-remi-gmail) -- acgvision-agent: package description formating issues https://bugs.launchpad.net/bugs/590971 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 592261] Re: The software does not work with icedtea
The problem came from the dep given by jh_depends. As the project doest not use it since the 5.1.4-6, there is no more bug. ** Changed in: acgvision-agent (Debian) Status: New = Fix Released ** Changed in: acgvision-agent (Debian) Assignee: (unassigned) = Remi Debay (debay-remi-gmail) ** Changed in: acgvision-agent (Ubuntu) Assignee: (unassigned) = Remi Debay (debay-remi-gmail) ** Changed in: acgvision-agent Status: New = Fix Released -- The software does not work with icedtea https://bugs.launchpad.net/bugs/592261 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 611053] [NEW] dell D505 won't work in try mode 10.04 LTS
Public bug reported: with live-cd 9.10 I386 OK work in try mode without installation with live-cd 10.04 LTS i386 netbook or and desktop, i can choose language, starting in try mode without installation , video is OK, but at the end of starting process (1,2,3,4,5 point from grey to red many times) KP. after bloc of strange pixel in center of screen. Same CD work on apple MBPro ;-) try with vga=771 and remove quiet also KP under ubuntu 9.10 with lshw dmidecode report Dell Inc. 0H2049 Bios vers: A07 09/03/2004 Not Specified 1700 MHz CPU-model 13 = Bus info Device Class Description p...@:00:02.0 display82852/855GM Integrated Graphics Device [8086:3582] p...@:00:02.1 display82852/855GM Integrated Graphics Device [8086:3582] p...@:00:1f.1 scsi0 storage82801DBM (ICH4-M) IDE Controller [8086:24CA] u...@1:3 scsi2 storage p...@:00:1f.5 multimedia 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24C5] p...@:01:03.0 eth1networkPRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] p...@:01:08.0 eth0network82801DB PRO/100 VE (MOB) Ethernet Controller [8086:103D] p...@:00:1d.0 bus82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24C2] p...@:00:1d.1 bus82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24C4] p...@:00:1d.2 bus82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24C7] p...@:00:1d.7 bus82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24CD] p...@:01:01.1 busPCI4510 IEEE-1394 Controller [104C:8029] = /proc/asound/oss/sndstat:0: Intel 82801DB-ICH4 (DUPLEX) /proc/asound/oss/sndstat:0: SigmaTel STAC9750,51 Model: ATA HTS548060M9AT00 (scsi) Disk /dev/sda: 60.0GB Partition Table: msdos Number Start End SizeType File system Flags 1 32.3kB 82.3MB 82.2MB primary fat16 2 82.3MB 26.3GB 26.2GB primary ntfs boot 3 26.3GB 60.0GB 33.7GB extended lba 5 26.3GB 60.0GB 33.7GB logical ntfs Model: USB2.0 USB Flash Disk (scsi) Disk /dev/sdb: 2055MB == 778M ram ** Affects: ubuntu Importance: Undecided Status: New -- dell D505 won't work in try mode 10.04 LTS https://bugs.launchpad.net/bugs/611053 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 590971] Re: acgvision-agent: package description formating issues
** Changed in: acgvision-agent (Ubuntu) Status: New = Confirmed -- acgvision-agent: package description formating issues https://bugs.launchpad.net/bugs/590971 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 305754] Re: p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1)
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: remi 1509 F pulseaudio /dev/snd/controlC0: remi 1509 F pulseaudio /dev/snd/pcmC1D0p: remi 1509 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 Card1.Amixer.info: Card hw:1 'Speaker'/'Logitech Logitech USB Speaker at usb-:00:02.0-1, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:0a04' Controls : 6 Simple ctrls : 5 Card2.Amixer.info: Card hw:2 'CX8811'/'Conexant CX8811 at 0xd300' Mixer name : 'CX88' Components : '' Controls : 3 Simple ctrls : 2 CheckboxSubmission: e28aba14c0315f1ed4ab278ba86b061e CheckboxSystem: edda5d4f616ca792bf437989cb597002 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=a94b6667-9661-44ec-a11e-8010ea2beb23 MachineType: TARGA System Product Name Package: linux (not installed) ProcCmdLine: root=UUID=7f8e98b0-f37c-4621-b738-5f968e88fc24 ro quiet splash ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Regression: Yes RelatedPackageVersions: linux-firmware 1.34 Reproducible: Yes RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: lucid networking regression-release needs-upstream-testing Uname: Linux 2.6.32-22-generic x86_64 UserGroups: adm admin audio cdrom dialout fuse lp lpadmin netdev plugdev sambashare video WpaSupplicantLog: dmi.bios.date: 01/25/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: Asus A8N-E ACPI BIOS Revision 0202 Targa dmi.board.name: A8N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrAsusA8N-EACPIBIOSRevision0202Targa:bd01/25/2006:svnTARGA:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: TARGA ** Changed in: linux (Ubuntu) Status: Expired = Incomplete ** Tags added: apport-collected -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/51130809/AlsaDevices.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/51130811/AplayDevices.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Card0.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt http://launchpadlibrarian.net/51130821/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/51130813/ArecordDevices.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/51130816/BootDmesg.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/51130818/Card0.Amixer.values.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Card1.Amixer.values.txt
apport information ** Attachment added: Card1.Amixer.values.txt http://launchpadlibrarian.net/51130822/Card1.Amixer.values.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Card0.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt http://launchpadlibrarian.net/51130819/Card0.Codecs.codec97.0.ac97.0.0.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Card2.Amixer.values.txt
apport information ** Attachment added: Card2.Amixer.values.txt http://launchpadlibrarian.net/51130823/Card2.Amixer.values.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/51130824/CurrentDmesg.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/51130832/Lspci.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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 305754] Lsusb.txt
apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/51130833/Lsusb.txt -- p54pci module freezes the system when loaded with a Netgear WG511 pcmcia wifi card (v1) https://bugs.launchpad.net/bugs/305754 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
