Re: [Bug 1964387] Re: pysol.py crashed with ModuleNotFoundError in /usr/share/games/pysolfc/pysollib/ui/tktile/tkhtml.py: No module named 'formatter'
I have been using the flatpak version, and it works. On Thu, Mar 21, 2024 at 5:31 PM Sudip Mukherjee <1964...@bugs.launchpad.net> wrote: > The upstream patch at > > https://github.com/shlomif/PySolFC/commit/79d27d2749c906040073909a2a7c1162282b806c > will need changes in the copyright file and has been discussed at > https://bugs.launchpad.net/ubuntu/+source/pysolfc/+bug/1967793/comments/8 > > ** Changed in: pysolfc (Ubuntu Jammy) > Assignee: Sudip Mukherjee (sudipmuk) => (unassigned) > > ** Changed in: pysolfc (Ubuntu Mantic) > Assignee: Sudip Mukherjee (sudipmuk) => (unassigned) > > ** Changed in: pysolfc (Ubuntu Noble) > Assignee: Sudip Mukherjee (sudipmuk) => (unassigned) > > ** Changed in: pysolfc (Ubuntu Jammy) >Status: In Progress => Confirmed > > ** Changed in: pysolfc (Ubuntu Mantic) >Status: In Progress => Confirmed > > ** Changed in: pysolfc (Ubuntu Noble) >Status: In Progress => Confirmed > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2043814). > https://bugs.launchpad.net/bugs/1964387 > > Title: > pysol.py crashed with ModuleNotFoundError in > /usr/share/games/pysolfc/pysollib/ui/tktile/tkhtml.py: No module named > 'formatter' > > Status in pysolfc package in Ubuntu: > Confirmed > Status in pysolfc source package in Jammy: > Confirmed > Status in pysolfc source package in Mantic: > Confirmed > Status in pysolfc source package in Noble: > Confirmed > Status in pysolfc package in Debian: > New > > Bug description: > just trying to play the game. this OS is up to date > > ProblemType: Crash > DistroRelease: Ubuntu 22.04 > Package: pysolfc 2.6.4-3 > ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 > Uname: Linux 5.15.0-22-generic x86_64 > ApportVersion: 2.20.11-0ubuntu78 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: XFCE > Date: Wed Mar 9 12:50:56 2022 > ExecutablePath: /usr/share/games/pysolfc/pysol.py > InstallationDate: Installed on 2022-03-08 (1 days ago) > InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 > (20220307) > InterpreterPath: /usr/bin/python3.10 > PackageArchitecture: all > ProcCmdline: /usr/bin/python3 /usr/games/pysolfc > Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, > 3.10.1-0ubuntu1 > PythonArgs: ['/usr/games/pysolfc'] > PythonDetails: N/A > SourcePackage: pysolfc > Title: pysol.py crashed with ModuleNotFoundError in > /usr/share/games/pysolfc/pysollib/ui/tktile/tkhtml.py: No module named > 'formatter' > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pysolfc/+bug/1964387/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964387 Title: pysol.py crashed with ModuleNotFoundError in /usr/share/games/pysolfc/pysollib/ui/tktile/tkhtml.py: No module named 'formatter' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pysolfc/+bug/1964387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891324] Re: Groovy Gorilla GRUB won't install to MBR
Newer builds, including the 22.04 daily builds GRUB will install to MBR after Xubuntu is installed, but the installer can't be correctly directed to install on my machines BIOS/MBR. I must install, go to the Live version, then repair GRUB. The installer on all versions demands to install on an EFI/boot partition, and said EFI partition must be there during the install process, even though my machine is old enough that said EFI is not picked up during the boot process. On Sat, Dec 18, 2021, 4:30 AM Chris Guiver <1891...@bugs.launchpad.net> wrote: > Thank you for reporting this bug to Ubuntu. > > Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. > > See this document for currently supported Ubuntu releases: > https://wiki.ubuntu.com/Releases > > We appreciate that this bug may be old and you might not be interested > in discussing it any more. But if you are then please upgrade to the > latest Ubuntu version and re-test. If you then find the bug is still > present in the newer Ubuntu version, please add a comment here telling > us which new version it is in. > > ** Changed in: grub-installer (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891324 > > Title: > Groovy Gorilla GRUB won't install to MBR > > Status in grub-installer package in Ubuntu: > Incomplete > > Bug description: > Tried 3 different daily builds, multiple distributions on /dev/sda. > Can't install GRUB to /dev/sda or /dev/sda1 which is my / pqrtition, > either. Errors out and usually messes up the previous GRUB install. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: ubiquity 20.10.9 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu44 > Architecture: amd64 > CasperMD5CheckResult: pass > CasperVersion: 1.452 > Date: Wed Aug 12 08:01:22 2020 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- > LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200811) > SourcePackage: grub-installer > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891324 Title: Groovy Gorilla GRUB won't install to MBR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891324] Re: Groovy Gorilla GRUB won't install to MBR
Most computers built in the last 10 years use EFI firmware, which does not use an MBR, instead using GPT formatting and a boot partition for all but the smallest of drives. I didn't detect the problem in the early daily builds when I initially installed Groovy, only when I re-installed at the beta. On 11/14/20, jonas-ska <1891...@bugs.launchpad.net> wrote: > It's amazing that users with MBR are simply unable to install 20.10. The > only option is to install 20.04 and then upgrade. I can't understand how > such an evident bug passed all the testing. Nobody uses MBR anymore? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891324 > > Title: > Groovy Gorilla GRUB won't install to MBR > > Status in grub-installer package in Ubuntu: > Confirmed > > Bug description: > Tried 3 different daily builds, multiple distributions on /dev/sda. > Can't install GRUB to /dev/sda or /dev/sda1 which is my / pqrtition, > either. Errors out and usually messes up the previous GRUB install. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: ubiquity 20.10.9 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu44 > Architecture: amd64 > CasperMD5CheckResult: pass > CasperVersion: 1.452 > Date: Wed Aug 12 08:01:22 2020 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- > LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200811) > SourcePackage: grub-installer > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891324 Title: Groovy Gorilla GRUB won't install to MBR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891324] [NEW] Groovy Gorilla GRUB won't install to MBR
Public bug reported: Tried 3 different daily builds, multiple distributions on /dev/sda. Can't install GRUB to /dev/sda or /dev/sda1 which is my / pqrtition, either. Errors out and usually messes up the previous GRUB install. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Wed Aug 12 08:01:22 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200811) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.9 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891324 Title: Groovy Gorilla GRUB won't install to MBR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644982] [NEW] package postfix-sqlite 3.1.3-4 failed to install/upgrade: trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2
Public bug reported: Keeps showing up shortly after login. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: postfix-sqlite 3.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 15 18:02:39 2016 DuplicateSignature: package:postfix-sqlite:3.1.3-4 Unpacking postfix-sqlite (3.1.3-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-6Rlqn8/46-postfix-sqlite_3.1.3-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2 ErrorMessage: trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2 InstallationDate: Installed on 2016-11-04 (22 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20161103) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: postfix Title: package postfix-sqlite 3.1.3-4 failed to install/upgrade: trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644982 Title: package postfix-sqlite 3.1.3-4 failed to install/upgrade: trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1644982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644982] Re: package postfix-sqlite 3.1.3-4 failed to install/upgrade: trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2
This install of zappity which has been in use for about 2 weeks now, and have upgraded at least 4 times. I keep thinking it will be fixed by the next upgrade, using apt-get because the update manager keeps failing with an error on a Mate desktop repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644982 Title: package postfix-sqlite 3.1.3-4 failed to install/upgrade: trying to overwrite '/usr/lib/postfix/postfix-sqlite.so.1.0.1', which is also in package postfix 3.1.3-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1644982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637732] [NEW] Can't configure apt-on-cd Ubuntu Mate 17.04 daily
Public bug reported: Attempting to install from live USB, install failed twice attempting to install further packages from the USB. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 16.10.14 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Sat Oct 29 10:34:21 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20161029) ProcEnviron: TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-16.10.14 ubuntu-mate zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637732 Title: Can't configure apt-on-cd Ubuntu Mate 17.04 daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509302] Re: package virtualbox 5.0.4-dfsg-2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
This affects me also, after removing virtualbox 4.3, could not install via Ubuntu Software Center on Xubuntu 15.10 Wiley. Downloaded the .deb for VirtualBox 5.0.4-dfsg-2. This attempt failed to install via gdebi/dpkg. Attempted to install via Synaptic, which kicked me here as a duplicated error. VirtualBox-qt and VirtualBox-dkms reported installation failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509302 Title: package virtualbox 5.0.4-dfsg-2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1509302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1078695] Re: xrandr : Failed to get size of gamma for output default
Have you tried the *vga=###* where ### is one of the valid VGA values, using this on the GRUB linux kernel line? This has worked for me on some recent kernels/x-servers where xrandr can't force the screen resolution. I have used this with *nouveau.noaccel=1* and sometimes *acpi=off* in problem situations to force the resolution where hardware acceleration enabled just causes the graphics processor to freeze, causing a reboot necessary. This does NOT work on GNOME, KDE, Unity, Cinnamon, etc., but does work for Mate and Xfce without Compiz enabled. Hope this helps. Carl Snyder On Thu, Sep 3, 2015 at 4:45 PM, BJB <1078...@bugs.launchpad.net> wrote: > Trying to solve #874694 (only getting 640x480 maximum resolution instead > of 1024x768), I see also an Amilo L6820 with Intel 82845G/GL/GE Chipset. > This blocks my attempts to force the screen resolution at xrandr level. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1078695 > > Title: > xrandr : Failed to get size of gamma for output default > > Status in x11-utils package in Ubuntu: > Confirmed > > Bug description: > I have been tracking in the Ubuntu & Linux Mint forums when people have > problems with the resolution of their screens not being able to be set to > the native resolution of their displays. Normally, that can be fixed by > either xrandr or xorg.conf settings, but occasionally when xrandr is typed > on a line by itself to check the configuration of the X display, the return > is [code]$ xrandr > xrandr : failed to get size of gamma for output default > Screen 0: blah blah > default : more blah blah[/code]When this has occurred, the output > maximum resolution can NOT be changed, and I haven't found any way to fix > the problem. > > [background] My particular rig is a custom built with a BIOStar N68S3B > motherboard, AMD Athlon II x3 processor, 8G RAM, nVidia GeForce 7025 > display adapter on the motherboard, Etronix 1701B display. I have > fought getting my maximum resolution (1280x1024) on this monitor since > 7.10 Gutsy Gibbon, and used a custom xorg.conf file until it stopped > working, around 9.10, and have used xrandr since. (I stopped using > Ubuntu as my primary OS of choice when Unity came out, because my rig > did not support Compiz or graphics acceleration. Xubuntu, Linux Mint > Debian Edition, or Debian are my primaries now.) The EDID on this > monitor is not read correctly/has never been read correctly, and I > have always been stuck with the default resolution on Live media, > except occasionally on Puppy or Elive, through two different main > machines. My first Linux install was on an eMachines T5212 with an > nVidia GeForce 6200 128M graphics memory, 2G RAM.[/Background] > > I noticed that on a Bodhi 2.0 Live media that the xrandr did not work > because x11-xserver-utils package was not installed. I was checking > out the Live media, because my Bodhi 2.0 virtual machine exhibits the > same problems reported by laptop users, that is, the Failed to get > size of gamma for output default and unable to use xrandr to add a > higher resolution display. When I added the x11-xserver-utils package > to the Live running install, I could use xrandr to properly get the > size of gamma and reset the display to 1280x1024. I re-installed from > the SAME live media to my Bodhi VirtualBox VM, still the same graphics > problem. x11-xserver-utils was installed during updates, but xrandr > still returned no gamma, display as 'default', and no ability to set > resolution higher than 1024x768 detected at install. > > I still have about 2 weeks laid-off from my primary work, so if there > is anything further I can do to help, just let me know. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078695 Title: xrandr : Failed to get size of gamma for output default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428880] [NEW] nvidia-304-updates 304.125-0ubuntu1: nvidia-304-updates kernel module failed to build
Public bug reported: error occurred when starting the desktop (Xubuntu). ProblemType: Package DistroRelease: Ubuntu 15.04 Package: nvidia-304-updates 304.125-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.19.0-7-generic Date: Sat Feb 28 20:15:21 2015 DuplicateSignature: dkms:nvidia-304-updates:304.125-0ubuntu1:/var/lib/dkms/nvidia-304-updates/304.125/build/nv.c:2029:30: error: ‘struct file’ has no member named ‘f_dentry’ InstallationDate: Installed on 2015-01-04 (60 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150103) PackageVersion: 304.125-0ubuntu1 SourcePackage: nvidia-graphics-drivers-304-updates Title: nvidia-304-updates 304.125-0ubuntu1: nvidia-304-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428880 Title: nvidia-304-updates 304.125-0ubuntu1: nvidia-304-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1428880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756818] Re: Unity Live session nvidia display unuseable
No real change in effect, Unity, GNOME 3.x, and Cinnamon still unusable. Hardware was changed to a BioStar N68S38 motherboard/Athlon II x3 processor/8G RAM/Graphics: Card: NVIDIA C61 [GeForce 7025 / nForce 630a] X.Org: 1.15.1 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1280x1024@60.0hz GLX Renderer: Gallium 0.4 on NV4C GLX Version: 2.1 Mesa 10.1.3 Monitor: Etronix 1701B 17 1280x1024 LCD display does not give proper edid I can now sometimes get a stable display on one of the three above DEs.until I attempt to actually open menu items, then the display freezes or goes for repeated pattern of dots on the screen, in either case the display freezes after a few seconds, requiring hard reset or power cycling Knoppix with LXDE Compiz works fine, as does Bodhi 2.x and 3.x and Xubuntu and Mate have remained working with no problems. I am thinking that all three of the above do not handle the case where the edid is not returned from the monitor to the computer acceptably. My only other monitor had been an old NEC Multisync II (800x600), but I obtained a Sansui model SLED 2900 I television/monitor and seeking confirmation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756818 Title: Unity Live session nvidia display unuseable To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/756818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756818] Re: Unity Live session nvidia display unuseable
The Sansui monitor trial reminded me that there are other outcomes beside the freezing and repeating pattern of dots. This trial set ALMOST worked from the trials of the LIVE disks of Unity, GNOME, KDE Plasma, and Cinnamon desktops, but random patterns made the display still unusable. The graphics did not freeze, and the nVidia proprietary driver may have worked, did not try in this set of trials. The other outcome which happened on Unity, GNOME/GNOME Classic and Cinnamon was to have yellow and white on white background for the screen text and other graphic elements, rendering most text onscreen unusable. BTW, the Sansui SLED2900I model was capable of 1280x1024. I tried Ubuntu 14.04 for Unity. Xubuntu 14.04 14.10 worked fine, as is PCLinuxOS LXDE. Next test would be to check using the nVidia proprietary driver and/or installed system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756818 Title: Unity Live session nvidia display unuseable To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/756818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756818] Re: Unity Live session nvidia display unuseable
With the Sansui monitor, I was able to install the nvidia-current package and get a stable display. nvidia-current had not helped with the Etronix 1701B monitor on which the edid was not read correctly. I am typing this on a Unity desktop on 14.04, so my problems seem to have been solved. I also tried on GNOME desktop with similar results. My problem seems to have been a combination of hardware (edid not reading properly) and driver (nouveau) not working together, and I will so report publicly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756818 Title: Unity Live session nvidia display unuseable To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/756818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1078695] Re: xrandr : Failed to get size of gamma for output default
I am not having the error under the present kernel 14.04 and open source driver. I have had the error while using nvidia-current and previous kernels and once using the nvidia open source driver and Xubuntu 13.10. Also had the reported problem with Bodhi (based on 12.04 at the time.) I updated to Xubuntu 14.04 pre-alpha and have not had any problems to report with this version. The last trial I made with Ubuntu 14.04, same setup, my graphics froze, diagonal random graphics, requiring a hard reboot to recover, but I have had similar problems with Ubuntu Unity since Unity was introduced, running on my desktop. My Acer Aspire One ZG5 netbook with Intel graphics has never had this problem, nor the freezing with Unity desktop. On Sat, Apr 26, 2014 at 4:25 PM, Ketil Malde ke...@malde.org wrote: I don't know if it is relevant here, but I got the same response from xrandr (about gamma), and also struggled with wrong resolutions. For me, the cause was the 'nomodeset' kernel parameter, this (i.e. disabling kernel modesetting) caused the i915 graphics driver to fail, and the vesa driver to be used instead. Perhaps you can check in /var/log/Xorg.0.log that the correct driver is being used? The log also contains the kernel command linke - although you may have to use 'nomodeset' to get nvidia to work (that was the reason it was in mine - when I removed the graphics card, I forgot to revert the grub options). -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1078695 Title: xrandr : Failed to get size of gamma for output default Status in “x11-utils” package in Ubuntu: Confirmed Bug description: I have been tracking in the Ubuntu Linux Mint forums when people have problems with the resolution of their screens not being able to be set to the native resolution of their displays. Normally, that can be fixed by either xrandr or xorg.conf settings, but occasionally when xrandr is typed on a line by itself to check the configuration of the X display, the return is [code]$ xrandr xrandr : failed to get size of gamma for output default Screen 0: blah blah default : more blah blah[/code]When this has occurred, the output maximum resolution can NOT be changed, and I haven't found any way to fix the problem. [background] My particular rig is a custom built with a BIOStar N68S3B motherboard, AMD Athlon II x3 processor, 8G RAM, nVidia GeForce 7025 display adapter on the motherboard, Etronix 1701B display. I have fought getting my maximum resolution (1280x1024) on this monitor since 7.10 Gutsy Gibbon, and used a custom xorg.conf file until it stopped working, around 9.10, and have used xrandr since. (I stopped using Ubuntu as my primary OS of choice when Unity came out, because my rig did not support Compiz or graphics acceleration. Xubuntu, Linux Mint Debian Edition, or Debian are my primaries now.) The EDID on this monitor is not read correctly/has never been read correctly, and I have always been stuck with the default resolution on Live media, except occasionally on Puppy or Elive, through two different main machines. My first Linux install was on an eMachines T5212 with an nVidia GeForce 6200 128M graphics memory, 2G RAM.[/Background] I noticed that on a Bodhi 2.0 Live media that the xrandr did not work because x11-xserver-utils package was not installed. I was checking out the Live media, because my Bodhi 2.0 virtual machine exhibits the same problems reported by laptop users, that is, the Failed to get size of gamma for output default and unable to use xrandr to add a higher resolution display. When I added the x11-xserver-utils package to the Live running install, I could use xrandr to properly get the size of gamma and reset the display to 1280x1024. I re-installed from the SAME live media to my Bodhi VirtualBox VM, still the same graphics problem. x11-xserver-utils was installed during updates, but xrandr still returned no gamma, display as 'default', and no ability to set resolution higher than 1024x768 detected at install. I still have about 2 weeks laid-off from my primary work, so if there is anything further I can do to help, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078695 Title: xrandr : Failed to get size of gamma for output default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196520] [NEW] package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to install/upgrade: package linux-image-3.8.0-19-generic is not ready for configuration cannot configure (current status `ha
Public bug reported: Just installed xubuntu in /dev/sda11, with updates installed during installation. After the initial updates and installation, there were additional updates to 80 packages, including the kernel. What looked to be the final action prior to finishing the update process was to install the kernel update, during which the computer froze for over 10 minutes. I hit the reset button and was unable to boot the system from the hard drive. Booted from a Live DVD of Xubuntu and was unable to detect my hard drive. Installed gparted and still was unable to detect /dev/sda. Re-booted from Xubuntu Live and was able to get to GRUB, going to Xubuntu. This is the second re-boot of Xubuntu, the first of which I tried apt-get update apt-get -f install . Both times a crash was reported and attempted to report the crash both times, this time successfully. I still have 39 or 40 updates listed by the update manager. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8 AptOrdering: linux-image-3.8.0-19-generic: Configure Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 1757 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 1 08:29:49 2013 DuplicateSignature: Unpacking replacement libxrender1:i386 ... Log started: 2013-07-01 08:29:49 dpkg: error processing linux-image-3.8.0-19-generic (--configure): package linux-image-3.8.0-19-generic is not ready for configuration ErrorMessage: package linux-image-3.8.0-19-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=68a199aa-e6c7-43f5-8d53-38b2df382884 InstallationDate: Installed on 2013-07-01 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 002 Device 002: ID 046d:c05a Logitech, Inc. Optical Mouse M90 Bus 002 Device 003: ID 0e8f:0022 GreenAsia Inc. Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: BIOSTAR Group N68S3B MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=f71dd1ba-bbe0-402c-ab0f-ecccb76e71f9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 RfKill: SourcePackage: linux Title: package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to install/upgrade: package linux-image-3.8.0-19-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: N68S3B dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/12/2010:svnBIOSTARGroup:pnN68S3B:pvr:rvnBIOSTARGroup:rnN68S3B:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.name: N68S3B dmi.sys.vendor: BIOSTAR Group ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196520 Title: package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to install/upgrade: package linux-image-3.8.0-19-generic is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196520] Re: package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to install/upgrade: package linux-image-3.8.0-19-generic is not ready for configuration cannot configure (current status `half
I was able to complete the installation by re-installing the 3.8.0-19-generic kernel using apt-get install , then I did an apt-get update apt-get dist-upgrade -y and the installation seems to be fine. I have no indication which I understand as to why the problem occurred, but my Xubuntu installation seems to be working fine. I was able to use the PPA for LibreOffice pre-releases to install LibreOffice Writer Calc 4.1 and separately install Chromium with no noted errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196520 Title: package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to install/upgrade: package linux-image-3.8.0-19-generic is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078695] Re: xrandr : Failed to get size of gamma for output default
I found a fix for the 'failed to get size of gamma for output default' which was causing the problems keeping the higher resolutions from being used. In using xrandr according to the https://wiki.ubuntu.com/X/Config/Resolution guide to add higher resolutions and xrandr returns the gamma error, I was able to fix the problem by adding --gamma 1:1:1 to the xrandr --output line, as follows: xrandr --output default --gamma 1:1:1 --mode 1280x1024 where xrandr returns the output name as default, and the modename is from a newly defined, higher resolution mode. I got this to work properly with my Etronix 1701B 1280x1024 pixel 17 LCD monitor from an Ubuntu 13.04 virtual machine which was reporting the gamma problem and display name 'default', with a Bodhi 2.0 virtual machine and a Bodhi 2.0 Live CD, all three exhibiting the 'default' display and 'failed to get size of gamma for output default'. The display does not immediately resize, but the new mode can be chosen from the arandr GUI. After selection, when the dialog box pops up, I select to keep that selection. On the next log out or restart, the default is at 1280x1024 as selected before, even at the login screen and at the desktop. Note: several modes greater than the previous 1024x768 maximum were also allowed, including modes which actually exceded the maximum of my monitor. I think this bug report can be closed, with proper documentation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078695 Title: xrandr : Failed to get size of gamma for output default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078695] Re: xrandr : Failed to get size of gamma for output default
I have a 'fix' for the bug which may work, but doesn't fix the underlying cause. If the proprietary drivers can be installed, or simply a different video driver, this may read the gamma and allow for re-sizing the display. I found a Live DVD (Linux Mint 14 Cinnamon) which caused the same problem of not reading the gamma, but when I installed nvidia-current under the Live session, I was able to get a gamma reading and re-size the display to add 1280x1024@60Hz. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078695 Title: xrandr : Failed to get size of gamma for output default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078695] [NEW] xrandr : Failed to get size of gamma for output default
Public bug reported: I have been tracking in the Ubuntu Linux Mint forums when people have problems with the resolution of their screens not being able to be set to the native resolution of their displays. Normally, that can be fixed by either xrandr or xorg.conf settings, but occasionally when xrandr is typed on a line by itself to check the configuration of the X display, the return is [code]$ xrandr xrandr : failed to get size of gamma for output default Screen 0: blah blah default : more blah blah[/code]When this has occurred, the output maximum resolution can NOT be changed, and I haven't found any way to fix the problem. [background] My particular rig is a custom built with a BIOStar N68S3B motherboard, AMD Athlon II x3 processor, 8G RAM, nVidia GeForce 7025 display adapter on the motherboard, Etronix 1701B display. I have fought getting my maximum resolution (1280x1024) on this monitor since 7.10 Gutsy Gibbon, and used a custom xorg.conf file until it stopped working, around 9.10, and have used xrandr since. (I stopped using Ubuntu as my primary OS of choice when Unity came out, because my rig did not support Compiz or graphics acceleration. Xubuntu, Linux Mint Debian Edition, or Debian are my primaries now.) The EDID on this monitor is not read correctly/has never been read correctly, and I have always been stuck with the default resolution on Live media, except occasionally on Puppy or Elive, through two different main machines. My first Linux install was on an eMachines T5212 with an nVidia GeForce 6200 128M graphics memory, 2G RAM.[/Background] I noticed that on a Bodhi 2.0 Live media that the xrandr did not work because x11-xserver-utils package was not installed. I was checking out the Live media, because my Bodhi 2.0 virtual machine exhibits the same problems reported by laptop users, that is, the Failed to get size of gamma for output default and unable to use xrandr to add a higher resolution display. When I added the x11-xserver-utils package to the Live running install, I could use xrandr to properly get the size of gamma and reset the display to 1280x1024. I re-installed from the SAME live media to my Bodhi VirtualBox VM, still the same graphics problem. x11-xserver-utils was installed during updates, but xrandr still returned no gamma, display as 'default', and no ability to set resolution higher than 1024x768 detected at install. I still have about 2 weeks laid-off from my primary work, so if there is anything further I can do to help, just let me know. ** Affects: x11-utils (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/1078695 Title: xrandr : Failed to get size of gamma for output default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1078695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022281] [NEW] package python3-distupgrade 1:0.168 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-ma
Public bug reported: Ubuntu Quantal VirtualBox install, July 8, 2012 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: python3-distupgrade 1:0.168 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 Date: Sun Jul 8 09:15:06 2012 DuplicateSignature: Unpacking python3-distupgrade (from .../python3-distupgrade_1%3a0.168_all.deb) ... dpkg: error processing /var/cache/apt/archives/python3-distupgrade_1%3a0.168_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-manager 1:0.164 ErrorMessage: trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-manager 1:0.164 InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120528) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Title: package python3-distupgrade 1:0.168 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-manager 1:0.164 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade package-conflict quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022281 Title: package python3-distupgrade 1:0.168 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-manager 1:0.164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1022281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022281] Re: package python3-distupgrade 1:0.168 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-mana
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022281 Title: package python3-distupgrade 1:0.168 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/DistUpgrade/utils.py', which is also in package python3-update-manager 1:0.164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1022281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019864] Re: update-manager crashed
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019864 Title: update-manager crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1019864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1017177] [NEW] update-manager crashed with ImportError in /usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeQuirks.py: No module named plugincore.manager
*** This bug is a duplicate of bug 1013490 *** https://bugs.launchpad.net/bugs/1013490 Public bug reported: Crash occurred when using Software Updater to attempt to update packages. I usually haven't been able to use the updater package, but have used apt-get or Synaptic to update Quantal packages. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.163 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu3 Architecture: amd64 Date: Sun Jun 24 11:40:28 2012 DuplicateOf: https://bugs.launchpad.net/bugs/1013490 ExecutablePath: /usr/bin/update-manager GsettingsChanges: InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120528) InterpreterPath: /usr/bin/python3.2mu PackageArchitecture: all ProcCmdline: /usr/bin/python3.2 /usr/bin/update-manager --dist-upgrade ProcCwd: /home/carl ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/update-manager', '--dist-upgrade'] SourcePackage: update-manager Title: update-manager crashed with ImportError in /usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeQuirks.py: No module named plugincore.manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017177 Title: update-manager crashed with ImportError in /usr/lib/python3/dist- packages/DistUpgrade/DistUpgradeQuirks.py: No module named plugincore.manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1017177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1017177] Re: update-manager crashed with ImportError in /usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeQuirks.py: No module named plugincore.manager
*** This bug is a duplicate of bug 1013490 *** https://bugs.launchpad.net/bugs/1013490 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017177 Title: update-manager crashed with ImportError in /usr/lib/python3/dist- packages/DistUpgrade/DistUpgradeQuirks.py: No module named plugincore.manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1017177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810721] Re: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()
Additional information which I noticed on my system: I didn't notice in Ubuntu 10.10 or prior (back to 7.10), but 11.10 definitely complains that my BIOS is not setting the interrupts, and I can see the screen where it complains after trying several times that my EDID is not acceptable. Don't know if this will help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810721 Title: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default() To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/810721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810721] Re: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()
I finally fixed my problem on WUBI and separate 11.10 install partition by adding kernel options to GRUB, ie. acpi=off noapic nomodeset Apparently my rig suffers from a regression on ACPI handling and the ATI Radeon Express 200 motherboard video, especially in the Linux Kernel 3.x strain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810721 Title: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default() To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/810721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810721] Re: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()
After kernel update from 3.0.0-10 to 3.0.0-11 on Xubuntu 11.10 beta, WUBI, same results as before, last 2 lines prior to freeze read: [numbers] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [numbers] ACPI: Power Button[PWRF] Presently running 2.6.38-11-generic kernel, Xubuntu 11.10 beta, default composit, ATI Radeon Express 200 graphics from the motherboard. Any other information available needed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810721 Title: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/810721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810721] Re: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()
My system was running with the older kernel because I get a halt at the point where the screen shows the power button is enabled running the 3.x kernel, and I never get to login. Running under Windows 7 32-bit WUBI, Xubuntu Session, update from 11.04 installation done Friday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810721 Title: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/810721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756818] Re: Unity Live session nvidia display unuseable
Following are my present .xsession-errors from the CD I created this morning. My display still blinks, but much slower, and my display comes back to the same display. It is usable. [begin file] /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=en_US. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. GNOME_KEYRING_CONTROL=/tmp/keyring-jqIaNB SSH_AUTH_SOCK=/tmp/keyring-jqIaNB/ssh GNOME_KEYRING_PID=4786 GNOME_KEYRING_CONTROL=/tmp/keyring-jqIaNB SSH_AUTH_SOCK=/tmp/keyring-jqIaNB/ssh GNOME_KEYRING_CONTROL=/tmp/keyring-jqIaNB SSH_AUTH_SOCK=/tmp/keyring-jqIaNB/ssh Window manager warning: Type mismatch: Expected `int' got `bool' for key /apps/metacity/general/num_workspaces Window manager warning: 0 stored in GConf key /apps/metacity/general/num_workspaces is out of range 1 to 36 Initializing nautilus-gdu extension (nautilus:4813): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed /usr/lib/python2.7/dist-packages/UpdateManager/SimpleGtkbuilderApp.py:35: GtkWarning: Ignoring the separator setting self.builder.add_from_file(path) WARNING:root:timeout reached, exiting ** (process:4823): DEBUG: desktop-launch-listener.vala:118: ran with uri: file:///home/ubuntu (nautilus:4813): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed Nautilus-Share-Message: Called net usershare info but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory Please ask your system administrator to enable user sharing. (nautilus:4813): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed ** (process:4823): DEBUG: desktop-launch-listener.vala:118: ran with uri: file:///home/ubuntu/.xsession-errors ** (process:4823): DEBUG: zeitgeist-datahub.vala:174: Inserting 1 events ** (process:4823): DEBUG: zeitgeist-datahub.vala:174: Inserting 3 events ** (process:4823): DEBUG: zeitgeist-datahub.vala:174: Inserting 1 events [end file] Any more information which I can provide? Operating with nVidia GeForce 6200. Note: I tried with the option to load only free software and didn't have this problem, either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756818 Title: Unity Live session nvidia display unuseable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756818] Re: Unity Live session nvidia display unuseable
I forgot to add to my previous comment, the desktop default seems to be GNOME, not Unity, for this download Live session. When I go to a terminal session, I get a nouveau error: DDC responded, but no EDID for VGA-1 As noted in my original report, my Etronix 1701B LCD display does not respond with a valid EDID, which I have been using /etc/X11/xorg.conf or xrandr to fix since Ubuntu 7.04. The default 1024x768@60Hz display is a valid mode for this monitor, which is 1280x1024. Should I try to install Natty to a flash drive persistent image to fix this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756818 Title: Unity Live session nvidia display unuseable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413624] Re: jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()
Happened on attempting to install Ubuntu 10.10 from the Linux Format magazine DVD on an Acer Aspire One ZG5, external DVD from Lite-On connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/413624 Title: jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555414] Re: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
I finally went into a terminal and used 'apt-get remove' to remove all of the error causing packages, one by one, then re-installed grub and other packages as needed to restore functioning and updating. As reported above, automatic re-configuring did not work. My system seems to be functioning now, I will append data if needed later. Thank you for your help and consideration. -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 555414] Re: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
I finally went into a terminal and used 'apt-get remove' to remove all of the error causing packages, one by one, then re-installed grub and other packages as needed to restore functioning and updating. As reported above, automatic re-configuring did not work. My system seems to be functioning now, I will append data if needed later. Thank you for your help and consideration. -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 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
Re: [Bug 555414] Re: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Attached find the terminal output from dpkg and the piped output file 'error.txt' I hope this tells you something. ** Attachment added: dpkg.out.txt http://launchpadlibrarian.net/43197335/dpkg.out.txt ** Attachment added: error.txt http://launchpadlibrarian.net/43197336/error.txt -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 555414] Re: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Attached find the terminal output from dpkg and the piped output file 'error.txt' I hope this tells you something. ** Attachment added: dpkg.out.txt http://launchpadlibrarian.net/43197335/dpkg.out.txt ** Attachment added: error.txt http://launchpadlibrarian.net/43197336/error.txt -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 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 555414] [NEW] package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Public bug reported: Binary package hint: samba Re-installation of Ubuntu 9.10 from LXFDVD127 after a Debian 5 re- installation accidentally overwrote Ubuntu / (/home was a separate partition and was not overwritten). Three partitions, /, /home, and swap, were the only partitions, sda1 (/ - ext4), sda2 (/home - ext3), and sda6 (swap) are used for Ubuntu, Debian uses sda5 (/ - ext3), sda7 (/home - ext3) and sda6 (swap). WinXP MC 2005 SP3 is installed on hda1, Win7 is installed on hda2. Initial installation went without any hitches. When installing upgrades, samba-common, grub-pc, and two other packages which I reported as failing with error 10, marked today as affecting me, failed on installation scripts. ProblemType: Package Architecture: i386 Date: Sun Apr 4 19:19:22 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: samba-common 2:3.4.0-3ubuntu5.6 PackageArchitecture: all ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: samba Title: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Uname: Linux 2.6.31-20-generic i686 ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 555414] [NEW] package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Public bug reported: Binary package hint: samba Re-installation of Ubuntu 9.10 from LXFDVD127 after a Debian 5 re- installation accidentally overwrote Ubuntu / (/home was a separate partition and was not overwritten). Three partitions, /, /home, and swap, were the only partitions, sda1 (/ - ext4), sda2 (/home - ext3), and sda6 (swap) are used for Ubuntu, Debian uses sda5 (/ - ext3), sda7 (/home - ext3) and sda6 (swap). WinXP MC 2005 SP3 is installed on hda1, Win7 is installed on hda2. Initial installation went without any hitches. When installing upgrades, samba-common, grub-pc, and two other packages which I reported as failing with error 10, marked today as affecting me, failed on installation scripts. ProblemType: Package Architecture: i386 Date: Sun Apr 4 19:19:22 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: samba-common 2:3.4.0-3ubuntu5.6 PackageArchitecture: all ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: samba Title: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Uname: Linux 2.6.31-20-generic i686 ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 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 555414] Re: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
** Attachment added: AptOrdering.txt http://launchpadlibrarian.net/43118171/AptOrdering.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43118172/Dependencies.txt ** Attachment added: Dmesg.txt http://launchpadlibrarian.net/43118173/Dmesg.txt ** Attachment added: DpkgTerminalLog.gz http://launchpadlibrarian.net/43118174/DpkgTerminalLog.gz -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/555414 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 414897] Re: [karmic] No sound with Realtek ALC883
I finally copied the ~/.pulse folder from an alternate user I set up to check if it was just the default user which had the problems with no sound. That fixed my problem, but I don't know why the alternate user worked and the original (default) user did not. -- [karmic] No sound with Realtek ALC883 https://bugs.launchpad.net/bugs/414897 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 414897] Re: [karmic] No sound with Realtek ALC883
I had installed with only a single user besides root. Using the guide to sound problems on the Ubuntu Forums, I added a different user. The new user sound works on my system. Now I just have to dig into what the differences are between the users. -- [karmic] No sound with Realtek ALC883 https://bugs.launchpad.net/bugs/414897 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 414897] Re: [karmic] No sound with Realtek ALC883
@Daniel T Chen I tried the rm -rf ~/.pulse* Still no sound. System Preferences Sound does not detect any sound hardware with the default user. sudo lshw for multimedia shows: *-multimedia description: Audio device product: IXP SB4x0 High Definition Audio Controller vendor: ATI Technologies Inc physical id: 14.2 bus info: p...@:00:14.2 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=HDA Intel latency=64 resources: irq:16 memory:9210-92103fff Is there any other information which I can provide with the aim of squashing this 'bug'? -- [karmic] No sound with Realtek ALC883 https://bugs.launchpad.net/bugs/414897 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 414897] Re: [karmic] No sound with Realtek ALC883
Running ALSA-Mixer from Terminal shows the Realtek ALC883 chip, HDA ATI SB motherboard sound package, but I am unable to get _any_ sound from Karmic. Sound had worked since I started with Gutsy, although PulseAudio since Intrepid had been problematical. Going to try disabling PulseAudio and going back to ALSA to see if that works. -- [karmic] No sound with Realtek ALC883 https://bugs.launchpad.net/bugs/414897 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 414546] Re: gdebi-gtk crashed with DebError in compressed_part_name()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/30401335/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/30401336/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/30401337/ProcStatus.txt ** Attachment added: Traceback.txt http://launchpadlibrarian.net/30401338/Traceback.txt ** Visibility changed to: Public -- gdebi-gtk crashed with DebError in compressed_part_name() https://bugs.launchpad.net/bugs/414546 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 386770] [NEW] package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy
Public bug reported: Binary package hint: lsb I was using sudo apt-get update followed by sudo apt-get upgrade in a terminal window when the crash occurred. Ubuntu 9.04, Jaunty Jackalope. I had a browser window open as well as the terminal window. The following is a copy of the attempted upgrade results from the terminal window. c...@cws-desktop:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: linux-headers-generic linux-image-generic linux-restricted-modules-generic The following packages will be upgraded: chromium-browser firefox firefox-3.0 firefox-3.0-branding firefox-3.0-gnome-support firefox-gnome-support hal imagemagick imagemagick-doc libaprutil1 libhal-storage1 libhal1 libmagickcore1 libmagickwand1 linux-libc-dev linux-restricted-modules-common lsb-base lsb-release tzdata xulrunner-1.9 xulrunner-1.9-gnome-support 21 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 34.2MB of archives. After this operation, 176kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://ppa.launchpad.net jaunty/main chromium-browser 3.0.189.0~svn20090612r18283-0ubuntu1~ucd2~jaunty [17.8MB] Get:2 http://us.archive.ubuntu.com jaunty-proposed/main lsb-base 4.0-0ubuntu0.9.04.1 [24.4kB] Get:3 http://us.archive.ubuntu.com jaunty-proposed/main tzdata 2009i-0ubuntu0.9.04 [694kB] Get:4 http://us.archive.ubuntu.com jaunty-proposed/main lsb-release 4.0-0ubuntu0.9.04.1 [23.9kB] Get:5 http://us.archive.ubuntu.com jaunty-updates/main firefox-3.0-branding 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [202kB] Get:6 http://us.archive.ubuntu.com jaunty-updates/main xulrunner-1.9-gnome-support 1.9.0.11+build2+nobinonly-0ubuntu0.9.04.1 [39.4kB] Get:7 http://us.archive.ubuntu.com jaunty-updates/main xulrunner-1.9 1.9.0.11+build2+nobinonly-0ubuntu0.9.04.1 [7549kB] Get:8 http://us.archive.ubuntu.com jaunty-updates/main firefox-3.0-gnome-support 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [84.7kB] Get:9 http://us.archive.ubuntu.com jaunty-updates/main firefox-3.0 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [887kB] Get:10 http://us.archive.ubuntu.com jaunty-updates/main firefox 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [69.3kB] Get:11 http://us.archive.ubuntu.com jaunty-updates/main firefox-gnome-support 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [69.2kB] Get:12 http://us.archive.ubuntu.com jaunty-proposed/main libhal1 0.5.12~rc1+git20090403-0ubuntu3 [93.5kB] Get:13 http://us.archive.ubuntu.com jaunty-proposed/main libhal-storage1 0.5.12~rc1+git20090403-0ubuntu3 [22.7kB] Get:14 http://us.archive.ubuntu.com jaunty-proposed/main hal 0.5.12~rc1+git20090403-0ubuntu3 [395kB] Get:15 http://us.archive.ubuntu.com jaunty-updates/main libmagickwand1 7:6.4.5.4.dfsg1-1ubuntu3.1 [334kB] Get:16 http://us.archive.ubuntu.com jaunty-updates/main libmagickcore1 7:6.4.5.4.dfsg1-1ubuntu3.1 [1654kB] Get:17 http://us.archive.ubuntu.com jaunty-updates/main imagemagick 7:6.4.5.4.dfsg1-1ubuntu3.1 [86.9kB] Get:18 http://us.archive.ubuntu.com jaunty-updates/main imagemagick-doc 7:6.4.5.4.dfsg1-1ubuntu3.1 [3243kB] Get:19 http://us.archive.ubuntu.com jaunty-updates/main libaprutil1 1.2.12+dfsg-8ubuntu0.1 [72.4kB] Get:20 http://us.archive.ubuntu.com jaunty-proposed/main linux-libc-dev 2.6.28-13.44 [760kB] Get:21 http://us.archive.ubuntu.com jaunty-proposed/restricted linux-restricted-modules-common 2.6.28-13.17 [11.3kB] Fetched 34.2MB in 1min 32s (371kB/s) Preconfiguring packages ... (Reading database ... 213306 files and directories currently installed.) Preparing to replace lsb-base 3.2-20ubuntu4 (using .../lsb-base_4.0-0ubuntu0.9.04.1_all.deb) ... Unpacking replacement lsb-base ... dpkg: error processing /var/cache/apt/archives/lsb-base_4.0-0ubuntu0.9.04.1_all.deb (--unpack): trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy Errors were encountered while processing: /var/cache/apt/archives/lsb-base_4.0-0ubuntu0.9.04.1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) c...@cws-desktop:~$ Additional information needed? ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy NonfreeKernelModules: nvidia Package: lsb-base 3.2-20ubuntu4 PackageArchitecture: all SourcePackage: lsb Title: package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy Uname: Linux 2.6.28-12-generic i686 ** Affects: lsb (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy https://bugs.launchpad.net/bugs/386770 You received this bug notification because
[Bug 386770] Re: package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27875047/Dependencies.txt ** Attachment added: DpkgTerminalLog.gz http://launchpadlibrarian.net/27875048/DpkgTerminalLog.gz -- package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy https://bugs.launchpad.net/bugs/386770 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 386770] Re: package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy
** Description changed: Binary package hint: lsb I was using sudo apt-get update followed by sudo apt-get upgrade in a terminal window when the crash occurred. Ubuntu 9.04, Jaunty Jackalope. I had a browser window open as well as the terminal window. The following is a copy of the attempted upgrade results from the terminal window. c...@cws-desktop:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: linux-headers-generic linux-image-generic linux-restricted-modules-generic The following packages will be upgraded: chromium-browser firefox firefox-3.0 firefox-3.0-branding firefox-3.0-gnome-support firefox-gnome-support hal imagemagick imagemagick-doc libaprutil1 libhal-storage1 libhal1 libmagickcore1 libmagickwand1 linux-libc-dev linux-restricted-modules-common lsb-base lsb-release tzdata xulrunner-1.9 xulrunner-1.9-gnome-support 21 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 34.2MB of archives. After this operation, 176kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://ppa.launchpad.net jaunty/main chromium-browser 3.0.189.0~svn20090612r18283-0ubuntu1~ucd2~jaunty [17.8MB] Get:2 http://us.archive.ubuntu.com jaunty-proposed/main lsb-base 4.0-0ubuntu0.9.04.1 [24.4kB] Get:3 http://us.archive.ubuntu.com jaunty-proposed/main tzdata 2009i-0ubuntu0.9.04 [694kB] Get:4 http://us.archive.ubuntu.com jaunty-proposed/main lsb-release 4.0-0ubuntu0.9.04.1 [23.9kB] Get:5 http://us.archive.ubuntu.com jaunty-updates/main firefox-3.0-branding 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [202kB] Get:6 http://us.archive.ubuntu.com jaunty-updates/main xulrunner-1.9-gnome-support 1.9.0.11+build2+nobinonly-0ubuntu0.9.04.1 [39.4kB] Get:7 http://us.archive.ubuntu.com jaunty-updates/main xulrunner-1.9 1.9.0.11+build2+nobinonly-0ubuntu0.9.04.1 [7549kB] Get:8 http://us.archive.ubuntu.com jaunty-updates/main firefox-3.0-gnome-support 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [84.7kB] Get:9 http://us.archive.ubuntu.com jaunty-updates/main firefox-3.0 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [887kB] Get:10 http://us.archive.ubuntu.com jaunty-updates/main firefox 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [69.3kB] Get:11 http://us.archive.ubuntu.com jaunty-updates/main firefox-gnome-support 3.0.11+build2+nobinonly-0ubuntu0.9.04.1 [69.2kB] Get:12 http://us.archive.ubuntu.com jaunty-proposed/main libhal1 0.5.12~rc1+git20090403-0ubuntu3 [93.5kB] Get:13 http://us.archive.ubuntu.com jaunty-proposed/main libhal-storage1 0.5.12~rc1+git20090403-0ubuntu3 [22.7kB] Get:14 http://us.archive.ubuntu.com jaunty-proposed/main hal 0.5.12~rc1+git20090403-0ubuntu3 [395kB] Get:15 http://us.archive.ubuntu.com jaunty-updates/main libmagickwand1 7:6.4.5.4.dfsg1-1ubuntu3.1 [334kB] Get:16 http://us.archive.ubuntu.com jaunty-updates/main libmagickcore1 7:6.4.5.4.dfsg1-1ubuntu3.1 [1654kB] Get:17 http://us.archive.ubuntu.com jaunty-updates/main imagemagick 7:6.4.5.4.dfsg1-1ubuntu3.1 [86.9kB] Get:18 http://us.archive.ubuntu.com jaunty-updates/main imagemagick-doc 7:6.4.5.4.dfsg1-1ubuntu3.1 [3243kB] Get:19 http://us.archive.ubuntu.com jaunty-updates/main libaprutil1 1.2.12+dfsg-8ubuntu0.1 [72.4kB] Get:20 http://us.archive.ubuntu.com jaunty-proposed/main linux-libc-dev 2.6.28-13.44 [760kB] Get:21 http://us.archive.ubuntu.com jaunty-proposed/restricted linux-restricted-modules-common 2.6.28-13.17 [11.3kB] Fetched 34.2MB in 1min 32s (371kB/s) Preconfiguring packages ... (Reading database ... 213306 files and directories currently installed.) Preparing to replace lsb-base 3.2-20ubuntu4 (using .../lsb-base_4.0-0ubuntu0.9.04.1_all.deb) ... Unpacking replacement lsb-base ... dpkg: error processing /var/cache/apt/archives/lsb-base_4.0-0ubuntu0.9.04.1_all.deb (--unpack): trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy Errors were encountered while processing: /var/cache/apt/archives/lsb-base_4.0-0ubuntu0.9.04.1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) c...@cws-desktop:~$ + Note: Removed /etc/lsb-base-logging.sh and attempted to restart the + sudo apt-get upgrade , but the same error occurred. + Additional information needed? ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy NonfreeKernelModules: nvidia Package: lsb-base 3.2-20ubuntu4 PackageArchitecture: all SourcePackage: lsb Title: package lsb-base 3.2-20ubuntu4 failed to install/upgrade: trying to overwrite `/etc/lsb-base-logging.sh', which is also in package splashy Uname: Linux 2.6.28-12-generic i686 -- package lsb-base 3.2-20ubuntu4 failed to
[Bug 355119] Re: Ubuntu Jaunty Install--Screen mode does not fit display
Fixed in release version of Ubuntu 9.04 Jaunty Jackalope. ** Changed in: live-installer (Ubuntu) Status: New = Fix Released -- Ubuntu Jaunty Install--Screen mode does not fit display https://bugs.launchpad.net/bugs/355119 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 355119] Re: Ubuntu Jaunty Install--Screen mode does not fit display
** Description changed: - Binary package hint: live-installer + Binary package hint: installer On my system, while attempting to install Ubuntu Jaunty Jackalope Beta (as of 4/1/2009), the display often had controls off the edge of the screen, without scrolling available. The controls I needed to finish the installation were there, but abort options, etc. often only had half of the button and the sub-title off the screen, below or to the right. I have an nVidia 6200 processor board with an Etronix 1280x1024 monitor. I will list more information as requested, or full information on my display system is listed in an earlier bug report on X server. + + Re-tried with the installer from the boot menu-- same problem. + Information buttons for forward/backward are both off screen to the + right. -- Ubuntu Jaunty Install--Screen mode does not fit display https://bugs.launchpad.net/bugs/355119 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 293096] Re: nvidia Pentium D low graphics/unsupported modes
Verified fixed in 180.44 in Ubuntu Jaunty Jackalope Beta. Defaulted to 1024x...@60hz. Note: My Etronix display is still not recognized, but I can at least get a usable display which doesn't go to an unrecognized mode. ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: Confirmed = Fix Released -- nvidia Pentium D low graphics/unsupported modes https://bugs.launchpad.net/bugs/293096 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 355119] [NEW] Ubuntu Jaunty Install--Screen mode does not fit display
Public bug reported: Binary package hint: live-installer On my system, while attempting to install Ubuntu Jaunty Jackalope Beta (as of 4/1/2009), the display often had controls off the edge of the screen, without scrolling available. The controls I needed to finish the installation were there, but abort options, etc. often only had half of the button and the sub-title off the screen, below or to the right. I have an nVidia 6200 processor board with an Etronix 1280x1024 monitor. I will list more information as requested, or full information on my display system is listed in an earlier bug report on X server. ** Affects: live-installer (Ubuntu) Importance: Undecided Status: New -- Ubuntu Jaunty Install--Screen mode does not fit display https://bugs.launchpad.net/bugs/355119 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 293096] [NEW] nvidia Pentium D low graphics/unsupported modes
Public bug reported: Binary package hint: xorg Problem has persisted from at least 7.10 Gutsy through 8.10 Intrepid, Live CD or installed, restricted driver or open source. When installing or upgrading Ubuntu, I am unable to get any screens to display at higher than 800x600 resolution without a custom xorg.conf file (see attached). On occasion, display modes of 1650x something and/or refresh frequencies of 50 to 54Hz - which are undisplayable on my Etronix 1710B LCD monitor (1280x1024 max resolution) resulted from attempting to use the automatic settings. At that point, I reboot with the Live CD, remove the revised settings and start again from fresh. Once I have my custom xorg.conf file installed, as long as I don't attempt to change the nVidia driver, my system has been stable and usable. Since this happened every time I have attempted to install or upgrade Ubuntu since Dec. '07, I thought I should report it. The same problem affects Mandriva One 2008 Spring, Debian Lenny and Knoppix 5.1.1 and 5.3.1. Many Live CD versions simply don't work on this machine configuration. I have a motherboard ATI graphics system, but was unable to get ANY Linux system to work with both sound and graphics until I installed a PCI express nVidia GeForce 6200 card and disabled the motherboard system. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: xorg 1:7.4~5ubuntu3 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.27-4-generic ([EMAIL PROTECTED]) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu7) ) #1 SMP Wed Sep 24 01:30:51 UTC 2008 SourcePackage: xorg Uname: Linux 2.6.27-4-generic i686 xkbcomp: ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- nvidia Pentium D low graphics/unsupported modes https://bugs.launchpad.net/bugs/293096 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 293096] Re: nvidia Pentium D low graphics/unsupported modes
** Attachment added: Custom xorg.conf file http://launchpadlibrarian.net/19283745/xorg.conf ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/19283746/Dependencies.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/19283747/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/19283748/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/19283749/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/19283750/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/19283751/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/19283753/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/19283754/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/19283756/xdpyinfo.txt -- nvidia Pentium D low graphics/unsupported modes https://bugs.launchpad.net/bugs/293096 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
