[Bug 1172908] Re: [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
Christopher M. Penalver, not to be insistent, but I am part of the BugSquad and so far nobody said anything about closing a bug just because one of the affected users is not able to reproduce it. The issue IS reproducible; if not by the original reporter, by 9 other people that have marked this bug as "it affects me". If nobody comes forward to provide information related to this bug, after 60 days the bug will be automatically marked as "Invalid", but not before. Nearly all the commenters are against closing this bug; what you are asking them to do is overflow Launchpad with duplicate bug reports: this would lead to a massive invalidation due to bug duplication and to extreme complications in handling the bug, because of infinite copies of the bug report in the system. This is how it works; please, do not change the status again. ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172908 Title: [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1172908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172908] Re: [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
The bug is still confirmed, as different users have reported it and comfirmed they are experiencing it. Leaving "Invalid" on the Linux project, as bugs are tracked through the "linux" package in Ubuntu. Dariusz Duraj, it does not matter. The kernel still has a bug, and here's the right place to file the bug report. Also, the kernel is not the "vanilla" from kernel.org, it's beed modified and compiled on the Ubuntu project servers, so it may be a problem related to that. ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172908 Title: [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1172908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 703180] Re: 197b:2391 SD card reader inaccessible without pci bus rescan
Tried it, but after modprobe-ing all the built drivers in my system, it still doesn't work if I don't rescan.. On Fri, Feb 8, 2013 at 11:25 PM, James M. Leddy <703...@bugs.launchpad.net>wrote: > The driver from here may help: http://kernel.ubuntu.com/git?p=lexical > /lexical-jmb38x.git;a=summary > > > ** Also affects: linux via >http://bugzilla.kernel.org/show_bug.cgi?id=40802 >Importance: Unknown >Status: Unknown > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/703180 > > Title: > 197b:2391 SD card reader inaccessible without pci bus rescan > > Status in The Linux Kernel: > Unknown > Status in “linux” package in Ubuntu: > Incomplete > > Bug description: > This is a Dell XPS L501X laptop (the new ones with USB3 etc: > http://www.dell.com/us/p/xps-15/pd.aspx) > > The card reader neither shows up in lspci nor in lsusb (only device > connected via USB seems to be the internal webcam which works), so I > can't even figure out which model it is… > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: linux-image-2.6.35-24-generic-pae 2.6.35-24.42 > Regression: No > Reproducible: No > ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 > Uname: Linux 2.6.35-24-generic-pae i686 > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. > Architecture: i386 > ArecordDevices: > List of CAPTURE Hardware Devices >card 0: Intel [HDA Intel], device 0: ALC665 Analog [ALC665 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: pascal 1777 F pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'Intel'/'HDA Intel at 0xf090 irq 49' > Mixer name : 'Intel IbexPeak HDMI' > Components : 'HDA:10ec0665,1028046e,0013 > HDA:80862804,80860101,0010' > Controls : 29 > Simple ctrls : 13 > Card1.Amixer.info: >Card hw:1 'NVidia'/'HDA NVidia at 0xadefc000 irq 17' > Mixer name : 'Nvidia GPU 14 HDMI/DP' > Components : 'HDA:10de0014,10de0101,00100100' > Controls : 16 > Simple ctrls : 4 > Date: Sat Jan 15 05:06:50 2011 > Frequency: Once a day. > HibernationDevice: RESUME=UUID=e7d13dad-6e7f-4320-8b4f-98e29cfde6f0 > InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 > (20101007) > Lsusb: >Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching > Hub >Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >Bus 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc. >Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching > Hub >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. XPS L501X > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic-pae > root=UUID=b8eb30a4-6bd4-4d52-b356-8cb3431ba849 ro quiet splash > ProcEnviron: >LANG=en_US.UTF-8 >SHELL=/usr/bin/zsh > RelatedPackageVersions: linux-firmware 1.38.3 > SourcePackage: linux > dmi.bios.date: 11/26/2010 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A04 > dmi.board.name: 00CKNG > dmi.board.vendor: Dell Inc. > dmi.board.version: A04 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A04 > dmi.modalias: > dmi:bvnDellInc.:bvrA04:bd11/26/2010:svnDellInc.:pnXPSL501X:pvrA04:rvnDellInc.:rn00CKNG:rvrA04:cvnDellInc.:ct8:cvrA04: > dmi.product.name: XPS L501X > dmi.product.version: A04 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/703180/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703180 Title: 197b:2391 SD card reader inaccessible without pci bus rescan To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/703180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887987] [NEW] Please upgrade turbogears2 to 2.1 version
Public bug reported: Turbogears 2.0.3 is pretty old, and it causes incompatibility with some recent software, such as convirt. Refer to http://groups.google.com/group/turbogears/browse_thread/thread/6f209bd6a22d66c5/791918d036f1e1b4?lnk=gst&q=ubuntu#791918d036f1e1b4 for additional details. Thanks! ** Affects: turbogears2 (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/887987 Title: Please upgrade turbogears2 to 2.1 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/turbogears2/+bug/887987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887204] Re: dmraid does not recognize ESRT2 drives
** Attachment added: "dmraid-s-ccc-d" https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+attachment/2588614/+files/dmraid-s-ccc-d ** Summary changed: - dmraid does not recognize ESRT2 drives + dmraid does not recognize Intel ESRT2 drives -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887204 Title: dmraid does not recognize Intel ESRT2 drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887204] Re: dmraid does not recognize ESRT2 drives
** Attachment added: "dmraid-s" https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+attachment/2588613/+files/dmraid-s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887204 Title: dmraid does not recognize Intel ESRT2 drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887204] Re: dmraid does not recognize ESRT2 drives
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+attachment/2588612/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887204 Title: dmraid does not recognize Intel ESRT2 drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887204] Re: dmraid does not recognize ESRT2 drives
** Attachment added: "syslog" https://bugs.launchpad.net/bugs/887204/+attachment/2588611/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887204 Title: dmraid does not recognize Intel ESRT2 drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887204] [NEW] dmraid does not recognize Intel ESRT2 drives
Public bug reported: I am trying to install Ubuntu Server on a server with a Intel S5000VSA motherboard, which carries an Intel ESRT2 RAID controller. I have tried 2 configurations: RAID5 on 3 500GB SATA disks and RAID 1 on two of those, with the other disk set as RAID0 The installer is unable to activate those disks; in particular, with the previous RAID5 configuration the installer complained about the raid45 module missing; I have tried to rebuild the array with the RAID1 and RAID0 configuration, and now it is unable to activate the disks. dmraid -s recognizes the arrays as ddf1 arrays, while I'm pretty sure they should be isw or lsi. I'm attaching /var/log/syslog and the output of dmesg, dmraid -s and dmraid -s -ccc -d You can see that dmraid segfaulted when trying to activate the devices, my guess is either because when it tried to detect the disks awk was missing, or because it is looking for the dm-raid45 module, which is no longer present in the kernel tree. If you know of a way to solve this, please let me know. Thanks, Claudio ** Affects: dmraid (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/887204 Title: dmraid does not recognize Intel ESRT2 drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/887204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 863763] Re: ubuntu sleeps after some time of inactivity even though sleep is disabled on inactivity when plugged in
Confirmed on a Dell XPS L502X with ALL options disabled (even the "on-battery" ones). I'm not experiencing timmy's issue, though; my laptop suspends and I have to push the power button to "revive" it (but I lose network connection and so on; makes it impossible to have a download running while the computer is left unattended) --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/863763 Title: ubuntu sleeps after some time of inactivity even though sleep is disabled on inactivity when plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/863763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 511982] Re: Wrong /var/lib/plymouth/boot-duration
I cannot confirm this; my /var/lib/plymouth/shutdown-duration is an empty file, but it's there... claudio@Chuck:~$ file /var/lib/plymouth/shutdown-duration /var/lib/plymouth/shutdown-duration: empty claudio@Chuck:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu oneiric (development branch) Release:11.10 Codename: oneiric claudio@Chuck:~$ uname -a Linux Chuck 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:23:39 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/511982 Title: Wrong /var/lib/plymouth/boot-duration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/511982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830440] Re: skype: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
What about reintroducing libxss in the ia32libs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830440 Title: skype: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/830440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847664] Re: dependency problem with virtual package compiz-core-abiversion-20110703
I'm marking this as "Fix Released" because it seems to have been fixed in the latest update. I ran "sudo apt-get install unity" and it worked, allowing me to login with the full (and composite) interface. Pleas, feel free to reopen it if you still have this issue after trying to install unity. ** Changed in: compiz (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847664 Title: dependency problem with virtual package compiz-core- abiversion-20110703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/847664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847664] Re: dependency problem with virtual package compiz-core-abiversion-20110703
Forget it, it works if I choose it from lightdm login screen. My bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847664 Title: dependency problem with virtual package compiz-core- abiversion-20110703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/847664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847664] Re: dependency problem with virtual package compiz-core-abiversion-20110703
Well, in my case unity-2d is not working: no panel no applets, compiz keeps crashing.. I had to use metacity and install gnome-panel in order to get a usable (and that's a big word) system.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847664 Title: dependency problem with virtual package compiz-core- abiversion-20110703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/847664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847694] [NEW] Unity installation fails due to missing compiz-core-abiversion-20110703
Public bug reported: After today's update, compiz-core-abiversion-20110703 is no longer available in the repositories. Because of that, trying to install unity results in: == root@Chuck:~# apt-get install unity Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: unity : Depends: compiz but it is not going to be installed Depends: compiz-core-abiversion-20110703 but it is not installable Depends: compiz-plugins-main-default but it is not going to be installed E: Unable to correct problems, you have held broken packages. == This is confirmed on http://packages.ubuntu.com/oneiric/unity where compiz-core-abiversion-20110703 is marked as Package not available while being a dependency for unity. --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Affects: unity (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/847694 Title: Unity installation fails due to missing compiz-core- abiversion-20110703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/847694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843751] Re: Oneiric lacks screensaver configuration tool
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843751 Title: Oneiric lacks screensaver configuration tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/843751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843751] [NEW] Oneiric lacks screensaver configuration tool
Public bug reported: As from the summary, in Oneiric there is no tool to configure gnome-screensaver. To me, this seems a regression from Natty, which had the default Gnome screesaver configuration tool. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.1.5-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 Date: Wed Sep 7 12:07:11 2011 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to oneiric on 2011-06-29 (70 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric regression running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843751 Title: Oneiric lacks screensaver configuration tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/843751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804230] Re: unity-panel-service crashed with SIGSEGV in g_signal_emit_valist()
It affects me randomly, meaning that no matter what I'm doing (though most of the times I'm surfing the web), at some point I have, like Daryl, 45-60 seconds of non responsive computer and then unity crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804230 Title: unity-panel-service crashed with SIGSEGV in g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ido/+bug/804230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841672] Re: ssh-add does not unlock ssh keys
Here's the output: claudio@Chuck:~$ echo $SSH_AUTH_SOCK /tmp/keyring-TjsKLR/ssh ** Changed in: openssh (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841672 Title: ssh-add does not unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841672] [NEW] ssh-add does not unlock ssh keys
Public bug reported: When I execute ssh-add it asks for my keys passwords and confirms that they were unlocked, but when I try to ssh into a server I am asked for my password again via the ssh-askpass-gnome prompt. Here's an (edited and cut) version of my .ssh/config file: = VisualHostKey yes Host myhost1 Hostname myhost1.url User user PreferredAuthentications publickey IdentityFile ~/.ssh/id_dsa Compression yes Compressionlevel 6 Host myhost2 Hostname myhost2.url User user PreferredAuthentications publickey Compression no Host myhost3 myhost4 myhost5 Hostname myhost3.url User user PreferredAuthentications publickey Compression yes Compressionlevel 6 [...] = ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: ssh-askpass (not installed) ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 Date: Mon Sep 5 11:29:43 2011 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ssh-askpass UpgradeStatus: Upgraded to oneiric on 2011-06-29 (68 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841672 Title: ssh-add does not unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811039] Re: Rhythmbox segfaults at startup
Deleting rhythmbox DB (~/.local/share/rhythmbox/rhythmdb.xml) fixed the issue ** Changed in: rhythmbox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811039 Title: Rhythmbox segfaults at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/811039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811039] Re: Rhythmbox segfaults at startup
** Attachment added: "rhythmbox launch with -d option output" https://bugs.launchpad.net/bugs/811039/+attachment/2209747/+files/rhythmbox.debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811039 Title: Rhythmbox segfaults at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/811039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811039] [NEW] Rhythmbox segfaults at startup
Public bug reported: After a dist-upgrade, rhythmbox stopped working. The graphical interface appears, but it doesn't load the library and crashes with a "Segmentation Fault (core dumped)" error. Attached, the output of $ rhythmbox -d >> /tmp/rhythmbox.debug 2>&1 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: rhythmbox 2.90.1~20110329-1ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7 Uname: Linux 3.0.0-5-generic x86_64 Architecture: amd64 Date: Fri Jul 15 15:09:16 2011 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to oneiric on 2011-06-29 (16 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811039 Title: Rhythmbox segfaults at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/811039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649809] Re: the session settings manager can try starting before the login screen one exits
** Changed in: gnome-settings-daemon Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/649809 Title: the session settings manager can try starting before the login screen one exits To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/649809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 771272] Re: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched
On Wed, Apr 27, 2011 at 13:53, jh wrote: > Don't think it's that simple. The new agent is overriding the gnome > authentication agent, and you've now lost any keys that were > automagically loaded from the gnome keyring. > > Ah, now I understand: claudio@Chuck:~$ echo $SSH_AUTH_SOCK /tmp/keyring-ZK6XAP/ssh claudio@Chuck:~$ echo $SSH_AGENT_PID 1640 claudio@Chuck:~$ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-iRQvNKEv2225/agent.2225; export SSH_AUTH_SOCK; SSH_AGENT_PID=2226; export SSH_AGENT_PID; echo Agent pid 2226; So, maybe it means that polkit isn't capable of handling ECDSA keys, and it makes sense because when using seahorse to show the key properties, my ECDSA key is recognized as a 320 bit DSA key (see attachment). ** Attachment added: "Seahorse.png" https://bugs.launchpad.net/bugs/771272/+attachment/2091399/+files/Seahorse.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771272] [NEW] ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched
Public bug reported: Binary package hint: gnome-keyring I'm not sure I have described it correctly in the summary, but this is what happens: I run ssh-add in a new terminal and enter my passphrase, which is the same for my DSA and ECDSA key: the DSA identity is added, but the ECDSA gets the "Error reading response length from authentication socket. Could not add identity: /home/claudio/.ssh/id_ecdsa" error. I run ssh-agent, copy and paste the output in the terminal and re-run ssh-add. Both identities are correctly added: claudio@Chuck:~$ ssh-add Enter passphrase for /home/claudio/.ssh/id_dsa: Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa) Error reading response length from authentication socket. Could not add identity: /home/claudio/.ssh/id_ecdsa claudio@Chuck:~$ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK; SSH_AGENT_PID=3917; export SSH_AGENT_PID; echo Agent pid 3917; claudio@Chuck:~$ SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK; claudio@Chuck:~$ SSH_AGENT_PID=3917; export SSH_AGENT_PID; claudio@Chuck:~$ echo Agent pid 3917; Agent pid 3917 claudio@Chuck:~$ ssh-add Enter passphrase for /home/claudio/.ssh/id_dsa: Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa) Identity added: /home/claudio/.ssh/id_ecdsa (/home/claudio/.ssh/id_ecdsa) Here is the content of my ~/.ssh/ claudio@Chuck:~$ ls -l .ssh total 32 -rw-r--r-- 1 claudio claudio 726 2011-04-15 23:34 config -r 1 claudio claudio 751 2011-04-05 10:35 id_dsa -rw-r--r-- 1 claudio claudio 603 2011-04-05 10:34 id_dsa.pub -r 1 claudio claudio 444 2011-04-05 10:29 id_ecdsa -rw-r--r-- 1 claudio claudio 267 2011-04-05 10:23 id_ecdsa.pub -rw--- 1 claudio claudio 6402 2011-04-19 18:04 known_hosts -rw-r--r-- 1 claudio claudio 2760 2011-04-06 17:05 known_hosts.old ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2 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: Tue Apr 26 16:27:02 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to natty on 2011-04-03 (23 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771272] Re: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728301] Re: Unable to search for applications
I'm setting it as invalid, because it is working now. Thanks anyway for the help =) ** Changed in: unity Status: Confirmed => Invalid ** Changed in: unity-place-applications Status: Confirmed => Invalid ** Changed in: unity-place-applications (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728301 Title: Unable to search for applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728301] Re: Unable to search for applications
I don' know what changed, but I kept Unity disabled these days (I needed a "stable" system) and when I re-enabled it, unity-place-applications was working. I'm trying to reboot, now; I did what you asked right after re-enabling, so I'm not sure that unity-place-applications is working because of it or if it's just working. If it works, I'll close the bug; for the records, that's the output you asked for: = claudio@Jarvis:~$ pkill -f unity-applications-daemon claudio@Jarvis:~$ /usr/lib/unity-place-applications/unity-applications-daemon Error loading package indexes: Couldn't stat '/var/cache/software-center/xapian' (process:17092): unity-applications-daemon-DEBUG: daemon.vala:341: Building initial application menu (process:17092): unity-applications-daemon-DEBUG: daemon.vala:362: Indexing application menu (process:17092): libunity-DEBUG: unity-place.vala:772: No browser to export (process:17092): unity-applications-daemon-DEBUG: daemon.vala:229: Sections model already populated. We probably cloned it off Unity. Rebuilding. (process:17092): unity-applications-daemon-DEBUG: daemon.vala:246: The groups model already populated. We probably cloned it off Unity. Rebuilding. (process:17092): unity-applications-daemon-DEBUG: daemon.vala:246: The groups model already populated. We probably cloned it off Unity. Rebuilding. (process:17092): unity-applications-daemon-DEBUG: daemon.vala:431: Entry search listed 251 Installed apps in 9,741000ms for query: type:Application (process:17092): unity-applications-daemon-DEBUG: daemon.vala:455: Entry search found 20/648 Most Used apps in 87,332000ms for query 'NOT category:XYZ' (process:17092): unity-applications-daemon-DEBUG: daemon.vala:431: Entry search listed 0 Installed apps in 0,174000ms for query: type:Application AND ciao (process:17092): unity-applications-daemon-DEBUG: daemon.vala:455: Entry search found 0/0 Most Used apps in 1,961000ms for query 'app:(ciao*)' ** (process:17092): CRITICAL **: UnityPackageSearchResult* unity_package_searcher_search(UnityPackageSearcher*, const gchar*, guint, UnityPackageSort): assertion `searcher != NULL' failed (process:17092): unity-applications-daemon-CRITICAL **: unity_applications_place_daemon_add_pkg_search_result: assertion `results != NULL' failed Errore di segmentazione (core dump creato) = The last line is the italian translation of "Segmentation fault (core dump created)". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728301 Title: Unable to search for applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728301] Re: Unable to search for applications
It also doesn't work when using the global search, but in the screenshot you can see that I tried to filter my search with a "random" string (asdfghhjklòò) and the list of applications didn't change. I mean: I can't refine the application list shown in unity-place-applications using the search box; no matter what string I put there, the applications list doesn't change... ** Changed in: unity Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728301 Title: Unable to search for applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728301] Re: Unable to search for applications
** Attachment added: "Applications place behaviour" https://bugs.launchpad.net/bugs/728301/+attachment/1882366/+files/Unity.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728301 Title: Unable to search for applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728301] [NEW] Unable to search for applications
Public bug reported: Binary package hint: unity-place-applications If I try to search for an application through the search bar, search does not even start. Searching in files place, instead, works. See attached screenshot ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity-place-applications 0.2.34-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 Date: Thu Mar 3 09:48:18 2011 ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity-place-applications UpgradeStatus: Upgraded to natty on 2011-02-28 (2 days ago) ** Affects: unity-place-applications (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728301 Title: Unable to search for applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690381] Re: Speaker volume depends from rhytmbox setting
After rebooting, speaker volume is set to zero again, and volume entry in .gconf/apps/rhythmbox/state/%gconf.xml is -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690381 Title: Speaker volume depends from rhytmbox setting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690381] Re: Speaker volume depends from rhytmbox setting
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690381 Title: Speaker volume depends from rhytmbox setting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690381] [NEW] Speaker volume depends from rhytmbox setting
Public bug reported: Since Hardy, I upgrade my system to a devel release at some point between alpha1 and alpha5. Every time, I get a really annoying problem, which is that my speaker volume is zeroed when I log in. Every time I want to hear something from my laptop speakers, I have to open up alsamixer and raise the speaker volume. This problem, always REMAINS when the release becomes stable. Some days ago, as a consequence of a profile corruption, I had to delete my .gconf folder, and I found out that volume worked right. When I restored it from a backup, it stopped working again. I found out that for some strange reasons, this behavior depends upon a setting in .gconf/apps/rhythmbox/state/%gconf.xml I had an entry that was like Note the "value". I wiped it out, saved the file, restarted rhythmbox and the new line was restarting my session left me with a working speaker. So my "bug report" is: why on earth should the whole profile speaker setting depend on rhythmbox? I filed it as an "audio" bug, so apport should add some audio settings and file, but I disabled the package indication, which was set to pulseaudio that I don't think should be responsible for this. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claudio2008 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 44' Mixer name : 'SigmaTel STAC9205' Components : 'HDA:838476a0,10280228,00100204 HDA:14f12c06,14f1000f,0010' Controls : 18 Simple ctrls : 11 Date: Tue Dec 14 22:50:29 2010 ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: pulseaudio Symptom: audio Title: [SigmaTel STAC9205] pactl stat failed to find default card dmi.bios.date: 04/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.pulse.daemon.conf: 2010-02-02T16:04:25.638062 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690381 Title: Speaker volume depends from rhytmbox setting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446566] Re: Compiz not starting automatically on login
Confirming this behavior in Maverick, as philw85 said. Also, it happened to me after removing some packages through computerjanitor, but I have no clue about which one did create the issue. ** Changed in: compiz (Ubuntu) Status: New => Confirmed -- Compiz not starting automatically on login https://bugs.launchpad.net/bugs/446566 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 657684] Re: Brasero burns corrupted disks and 2MB images
** Attachment added: "brasero-hexdump" https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/657684/+attachment/1681676/+files/brasero-hexdump -- Brasero burns corrupted disks and 2MB images https://bugs.launchpad.net/bugs/657684 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 657684] Re: Brasero burns corrupted disks and 2MB images
** Attachment added: "brasero-session.log" https://bugs.edge.launchpad.net/bugs/657684/+attachment/1681674/+files/brasero-session.log -- Brasero burns corrupted disks and 2MB images https://bugs.launchpad.net/bugs/657684 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 657684] [NEW] Brasero burns corrupted disks and 2MB images
Public bug reported: Binary package hint: brasero Yesterday, I tried to burn a data disk containing a bunch of MP3 files. Burning completed, but checksum verification failed with similar errors as in bug #405165; In my case, though, the disk itself is corrupted. I first thought about a "normal" failed writing. Re-burning the disk resulted in the same problem (and got me a little bit angry). Today, I tried several times burning the same project on a disk image: brasero burned it at a strangely high speed, but said the image was 570+ MB; yet, checking the real size of the image showed me it was 2 MB. Mounting the ISO, showed the correct filesystem structure, but playing a random track resulted in errors. Note: I added files to the project by dragging and dropping them from Rhythmbox I _THINK_ I added one of the files by drag and drop from nautilus and it was the only file that correctly played in my car cd reader. Attaching brasero-session.log from the second disk burn and hexdump -C brasero.iso ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: brasero 2.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Oct 10 15:00:43 2010 ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash SourcePackage: brasero ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Brasero burns corrupted disks and 2MB images https://bugs.launchpad.net/bugs/657684 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 625832] Re: [Maverick] plymouth falls to text mode even if graphic mode worked before
Info: it worked and it's great (except for grub2, I need to reduce the resolution: 1440x900 is too much). I'm not trying any other plymouth theme, but if someone decides to try, let me know (even if the guide says it's best with non-HQ themes). One question: if I remove v86d and leave the FRAMEBUFFER=Y line in /etc /initramfs-tools/conf.d/splash, what can happen? (i'm scared of blowing something up, so I wont try it... now..) -- [Maverick] plymouth falls to text mode even if graphic mode worked before https://bugs.launchpad.net/bugs/625832 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 625832] Re: [Maverick] plymouth falls to text mode even if graphic mode worked before
@Steve, I'm following a guide which says I need to replace vesafb with uvesafb in order to make framebuffer work. One of the commands it says I have to launch is $ sudo hwinfo --framebuffer Here's the output I got (before installing v86d): r...@jarvis:~# hwinfo --framebuffer 02: None 00.0: 11001 VESA Framebuffer [Created at bios.464] Unique ID: rdCR.zrHRJLheAS6 Hardware Class: framebuffer Model: "NVIDIA G84 Board - p410h1b " Vendor: "NVIDIA Corporation" Device: "G84 Board - p410h1b " SubVendor: "NVIDIA" SubDevice: Revision: "Chip Rev" Memory Size: 14 MB Memory Range: 0xfb00-0xfbdf (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0303: 800x600 (+800), 8 bits Mode 0x0305: 1024x768 (+1024), 8 bits Mode 0x0307: 1280x1024 (+1280), 8 bits Mode 0x030e: 320x200 (+640), 16 bits Mode 0x030f: 320x200 (+1280), 24 bits Mode 0x0311: 640x480 (+1280), 16 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Mode 0x0317: 1024x768 (+2048), 16 bits Mode 0x0318: 1024x768 (+4096), 24 bits Mode 0x031a: 1280x1024 (+2560), 16 bits Mode 0x031b: 1280x1024 (+5120), 24 bits Mode 0x0330: 320x200 (+320), 8 bits Mode 0x0331: 320x400 (+320), 8 bits Mode 0x0332: 320x400 (+640), 16 bits Mode 0x0333: 320x400 (+1280), 24 bits Mode 0x0334: 320x240 (+320), 8 bits Mode 0x0335: 320x240 (+640), 16 bits Mode 0x0336: 320x240 (+1280), 24 bits Mode 0x033d: 640x400 (+1280), 16 bits Mode 0x033e: 640x400 (+2560), 24 bits Mode 0x0345: 1600x1200 (+1600), 8 bits Mode 0x0346: 1600x1200 (+3200), 16 bits Mode 0x0347: 1400x1050 (+1400), 8 bits Mode 0x0348: 1400x1050 (+2800), 16 bits Mode 0x0349: 1400x1050 (+5600), 24 bits Mode 0x034a: 1600x1200 (+6400), 24 bits Mode 0x0352: 2048x1536 (+8192), 24 bits Mode 0x0360: 1280x800 (+1280), 8 bits Mode 0x0361: 1280x800 (+5120), 24 bits Mode 0x0362: 768x480 (+768), 8 bits Mode 0x0364: 1440x900 (+1440), 8 bits Mode 0x0365: 1440x900 (+5760), 24 bits Mode 0x0368: 1680x1050 (+1680), 8 bits Mode 0x0369: 1680x1050 (+6720), 24 bits Mode 0x037c: 1920x1200 (+1920), 8 bits Mode 0x037d: 1920x1200 (+7680), 24 bits Config Status: cfg=new, avail=yes, need=no, active=unknown I'm looking at the last line: even if I don't know what it means with cfg=new (even if I know that cfg stands for config), I see that, in my opinion, framebuffer is available, not needed (understandable, as X.Org does his job), but it's impossible to determine whether it's active or not, which is my point: why does that happen? I'm just trying to guess, I hope you'll understand this better than me. Here's the guide I'm following (although I have not followed it completely yet, so I DO NOT RECOMMEND trying it. For what that matters :D) https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high- resolution-plymouth-virtual-terminal-for-atinvidia-cards-with- proprietaryrestricted-driver/ -- [Maverick] plymouth falls to text mode even if graphic mode worked before https://bugs.launchpad.net/bugs/625832 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 625832] Re: [Maverick] plymouth falls to text mode even if graphic mode worked before
** Changed in: linux (Ubuntu) Status: New => Confirmed -- [Maverick] plymouth falls to text mode even if graphic mode worked before https://bugs.launchpad.net/bugs/625832 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 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
On Tue, Sep 14, 2010 at 07:58, Steve Langasek wrote: > has anyone reproduced this nvidia+gdm crash on maverick? Marking > incomplete for maverick pending confirmation. > On my system, this bug was fixed. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 625832] Re: [Maverick] plymouth falls to text mode even if graphic mode worked before
The question is: why my FB is not available, if before it worked flawlessly? -- [Maverick] plymouth falls to text mode even if graphic mode worked before https://bugs.launchpad.net/bugs/625832 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 527721] Re: gnome randomly crashes back to GDM login screen
I'm experiencing it on Maverick, on a Dell Vostro 1500 and an NVidia GeForce 8600M GT. No mention about the crash either in dmesg or /var/log/dmesg (which I assume output the same text, but I checked both) clau...@jarvis:~$ apt-cache policy plymouth plymouth: Installato: 0.8.2-2ubuntu3 Candidato: 0.8.2-2ubuntu3 Tabella versione: *** 0.8.2-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status ** Changed in: gdm (Ubuntu) Status: Incomplete => Confirmed -- gnome randomly crashes back to GDM login screen https://bugs.launchpad.net/bugs/527721 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 625832] Re: [Maverick] plymouth falls to text mode even if graphic mode worked before
** Attachment added: "BootDmesg.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525039/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525040/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525041/+files/Dependencies.txt ** Attachment added: "Lspci.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525042/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525043/+files/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525044/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525045/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525046/+files/ProcModules.txt ** Attachment added: "UdevDb.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525047/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.edge.launchpad.net/bugs/625832/+attachment/1525048/+files/UdevLog.txt -- [Maverick] plymouth falls to text mode even if graphic mode worked before https://bugs.launchpad.net/bugs/625832 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 625832] [NEW] [Maverick] plymouth falls to text mode even if graphic mode worked before
Public bug reported: Binary package hint: plymouth I was able to see plymouth graphic mode until about 20 days ago. Then I went on holiday (so I cannot tell which version I was using before) and after upgrading my system, plymouth started to fall back to text mode. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: plymouth 0.8.2-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 28 15:52:35 2010 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth MachineType: Dell Inc. Vostro 1500 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-19-generic root=/dev/mapper/sda6_crypt ro quiet splash ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash ProcFB: SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth dmi.bios.date: 04/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- [Maverick] plymouth falls to text mode even if graphic mode worked before https://bugs.launchpad.net/bugs/625832 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 570233] Re: Computer boots to text when on battery power
** Changed in: plymouth (Ubuntu) Status: New => Confirmed -- Computer boots to text when on battery power https://bugs.launchpad.net/bugs/570233 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 537287] Re: The about window shows the indicator applet about information
added indicator-session as affected (from my dupe) ** Also affects: indicator-session Importance: Undecided Status: New ** Changed in: indicator-session Status: New => Confirmed -- The about window shows the indicator applet about information https://bugs.launchpad.net/bugs/537287 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 612593] Re: Wrong website link in information panel
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52888282/Dependencies.txt ** Description changed: Binary package hint: indicator-session - The website link in the information panel, links to - https://launchpad.net/indicator-applet, while it must point to - https://launchpad.net/indicator-session + The website link in the information panel links to https://launchpad.net + /indicator-applet, while it must point to https://launchpad.net + /indicator-session - ProblemType: Bug - DistroRelease: Ubuntu 10.10 + ProblemType: BugDistroRelease: Ubuntu 10.10 Package: indicator-session 0.2.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-12.17-generic 2.6.35-rc6 Uname: Linux 2.6.35-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 2 16:37:01 2010 ProcEnviron: - LANG=it_IT.utf8 - SHELL=/bin/bash - SourcePackage: indicator-session + LANG=it_IT.utf8 + SHELL=/bin/bashSourcePackage: indicator-session -- Wrong website link in information panel https://bugs.launchpad.net/bugs/612593 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 612593] [NEW] Wrong website link in information panel
Public bug reported: Binary package hint: indicator-session The website link in the information panel links to https://launchpad.net /indicator-applet, while it must point to https://launchpad.net /indicator-session ProblemType: BugDistroRelease: Ubuntu 10.10 Package: indicator-session 0.2.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-12.17-generic 2.6.35-rc6 Uname: Linux 2.6.35-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 2 16:37:01 2010 ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bashSourcePackage: indicator-session ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Wrong website link in information panel https://bugs.launchpad.net/bugs/612593 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 608954] Re: Caps Lock led is not triggered, no "Caps Lock enabled" message when cryptsetup asks for password
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/52338019/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/52338020/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52338021/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/52338022/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/52338023/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/52338024/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/52338025/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/52338026/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/52338027/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/52338028/UdevLog.txt -- Caps Lock led is not triggered, no "Caps Lock enabled" message when cryptsetup asks for password https://bugs.launchpad.net/bugs/608954 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 608954] [NEW] Caps Lock led is not triggered, no "Caps Lock enabled" message when cryptsetup asks for password
Public bug reported: Binary package hint: plymouth If one inadvertently presses the "Caps Lock" button and tries to enter his password, cryptsetup does not (obviously) accept it, but the user is not aware he's trying to enter a password that's different from his real one. I flagged it as a plymouth bug, as it is responsible for cryptsetup user interface. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: plymouth 0.8.2-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5 Uname: Linux 2.6.35-9-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jul 23 00:37:32 2010 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth MachineType: Dell Inc. Vostro 1500 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-9-generic root=/dev/mapper/sda6_crypt ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=it_IT.utf8 SHELL=/bin/bash ProcFB: 0 VESA VGA 1 VGA16 VGA SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth dmi.bios.date: 04/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Caps Lock led is not triggered, no "Caps Lock enabled" message when cryptsetup asks for password https://bugs.launchpad.net/bugs/608954 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 479323] Re: External monitor suddenly gets wrong resolution on laptop (nvidia).
I'm experiencing quite the same bug. On a Dell Vostro 1500 (NVIDIA GeForce 8600M GT), I have an external monitor with maximum resolution 1280x1024. The strange thing is that it's not happening every time I plug it in, but it happens randomly. In this moment, I'm looking at the external monitor, with the 1280x1024 resolution. Yesterday, for example, there was a moment when the resolution was not correctly set, and I found myself with a 1440x900 resolution fit in a 1024x768 (the screen moved as I moved my mouse - hope this is understandable, I'm Italian). Rebooting "fixed" it (although maybe at next reboot I'll find myself with the wrong resolution). greping /var/log/Xorg.* searching for "EDID" didn't show any result, but "get-edid|parse-edid" shows problems (I'm attaching the complete output): [some text..] VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed EDID claims 32 more blocks left *** Something special has happened! Please contact the author, Matthew Kern E-mail: pyrophobic...@gmail.com Please include full output from this program (especially that to stderr) [more text...] VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed parse-edid: EDID checksum failed - data is corrupt. Continuing anyway. parse-edid: first bytes don't match EDID version 1 header parse-edid: do not trust output (if any). [more text...] EDID claims 32 more blocks left EDID blocks left is wrong. Your EDID is probably invalid. ** Attachment added: "get-edid|parse-edid output" http://launchpadlibrarian.net/50666056/edid -- External monitor suddenly gets wrong resolution on laptop (nvidia). https://bugs.launchpad.net/bugs/479323 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 596748] Re: apport-bug --save /tmp/file.apport does not show Apport window and exits without doing anything
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/50665015/Dependencies.txt -- apport-bug --save /tmp/file.apport does not show Apport window and exits without doing anything https://bugs.launchpad.net/bugs/596748 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 596748] [NEW] apport-bug --save /tmp/file.apport does not show Apport window and exits without doing anything
Public bug reported: Binary package hint: apport When I launch "apport-bug" (without parameters) a window is shown, so I can explain the bug I'm experiencing. Launching "apport-bug --save /tmp/file.apport", does not show that window, but exits and does not save the report (as there's nothing to save, I guess, because I haven't provided the information needed to report it) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: apport 1.13.3-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia ApportLog: Architecture: amd64 Date: Mon Jun 21 07:40:32 2010 PackageArchitecture: all ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash SourcePackage: apport ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- apport-bug --save /tmp/file.apport does not show Apport window and exits without doing anything https://bugs.launchpad.net/bugs/596748 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 593321] Re: do-release-upgrade -d does not upgrade to Maverick even if Alpha1 has been released
I think you meant /etc/update-manager/release-upgrades It was "lts", I changed it to "normal" and now it works. Thanks for helping me, I'm marking this as Invalid :) ** Changed in: update-manager-core (Ubuntu) Status: Incomplete => Invalid -- do-release-upgrade -d does not upgrade to Maverick even if Alpha1 has been released https://bugs.launchpad.net/bugs/593321 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 593321] Re: do-release-upgrade -d does not upgrade to Maverick even if Alpha1 has been released
** Attachment added: "sources.list" http://launchpadlibrarian.net/50265860/sources.list -- do-release-upgrade -d does not upgrade to Maverick even if Alpha1 has been released https://bugs.launchpad.net/bugs/593321 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 593321] [NEW] do-release-upgrade -d does not upgrade to Maverick even if Alpha1 has been released
Public bug reported: Binary package hint: update-manager-core I am not able to upgrade from Lucid to Maverick with "do-release-upgrade -d" and "update-manager -d" as the latter shows nothing about a new release and the first has this behaviour: clau...@jarvis:~$ sudo do-release-upgrade -d Checking for a new ubuntu release No new release found My system is fully up to date, and I'm using default Canonical repos (not local mirrors) ; attaching my sources.list. ** Affects: update-manager-core (Ubuntu) Importance: Undecided Status: New -- do-release-upgrade -d does not upgrade to Maverick even if Alpha1 has been released https://bugs.launchpad.net/bugs/593321 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 571968] Re: upgrade from 9.10 Karmic to 10.04 Lucid aborted
*** This bug is a duplicate of bug 529318 *** https://bugs.launchpad.net/bugs/529318 Marked as a duplicate of #529318 as you suggested, Alpha =) ** This bug has been marked a duplicate of bug 529318 Removing transmission-daemon breaks dpkg ** Changed in: update-manager (Ubuntu) Status: Incomplete => Invalid -- upgrade from 9.10 Karmic to 10.04 Lucid aborted https://bugs.launchpad.net/bugs/571968 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 571968] Re: upgrade from 9.10 Karmic to 10.04 Lucid aborted
Let me know if it works; if not, we will try to find another solution (and confirm this bug). On Fri, Apr 30, 2010 at 11:50, Alpha wrote: > I followed the same method for 9.04 to 9.10 upgrade last time.Thanks as > suggested i will try updating through the physical cd. > > -- > upgrade from 9.10 Karmic to 10.04 Lucid aborted > https://bugs.launchpad.net/bugs/571968 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “update-manager” package in Ubuntu: Incomplete > > Bug description: > Binary package hint: update-manager > > Could not install the upgrades > > The upgrade is now aborted. Your system could be in an unusable state. A > recovery will run now (dpkg --configure -a). > > Please report this bug against the 'update-manager' package and include the > files in /var/log/dist-upgrade/ in the bug report. > E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process > /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg > returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error > code (1), E:Sub-process /usr/bin/dpkg returned an error code (2), > E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process > /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg > returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error > code (2), E:Sub-process /usr/bin/dpkg returned an error code (1), > E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process > /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg > returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error > code (1), E:Sub-process /usr/bin/dpkg returned an error code (2), > E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process > /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg > returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error > code (2), E:Sub-process /usr/bin/dpkg returned an error code (1), > E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process > /usr/bin/dpkg returned an error code (1) > > Packages such as bash,dash,gawk,grep.login were reported as not installed > in the upgrade > > al...@alpha-desktop:~$ apt-cache policy update-manager > update-manager: > Installed: 1:0.134.7 > Candidate: 1:0.134.7 > Version table: > *** 1:0.134.7 0 >500 cdrom://Ubuntu 10.04 LTS _Lucid Lynx_ - Release i386 > (20100427.1)/ lucid/main Packages >100 /var/lib/dpkg/status > al...@alpha-desktop:~$ uname -a > Linux alpha-desktop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 > UTC 2010 i686 GNU/Linux > al...@alpha-desktop:~$ lsb_release -a > LSB Version: > > core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch > Distributor ID: Ubuntu > Description:Ubuntu 10.04 LTS > Release:10.04 > Codename: lucid > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/571968/+subscribe > -- upgrade from 9.10 Karmic to 10.04 Lucid aborted https://bugs.launchpad.net/bugs/571968 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 571934] Re: System crashes during boot
I've changed the title of this bug report, because I'm not sure this crash can be related to a module; the last syslog line before the Call Trace is relatedto wpa_supplicant, which is not a kernel module. ** Summary changed: - kernel module crahs on boot + System crashes during boot -- System crashes during boot https://bugs.launchpad.net/bugs/571934 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 571968] Re: upgrade from 9.10 Karmic to 10.04 Lucid aborted
If I'm not wrong, the error occurred because the system could not find the Lucid cdrom. Have you upgraded in this way before? Can you try burning it and then trying to upgrade? ** Changed in: update-manager (Ubuntu) Status: New => Incomplete -- upgrade from 9.10 Karmic to 10.04 Lucid aborted https://bugs.launchpad.net/bugs/571968 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 571980] Re: crash on boot with kernel 2.6.32-21
** Summary changed: - crash on boot with kernal 2.6.32-21 + crash on boot with kernel 2.6.32-21 -- crash on boot with kernel 2.6.32-21 https://bugs.launchpad.net/bugs/571980 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 572011] Re: facebook is always a day or two OLD
Are you sure this is not a Facebook problem, instead of Gwibber? This can be due to FB server issues, can you please try another client and see if there's the same behaviour? ** Changed in: gwibber (Ubuntu) Status: New => Incomplete -- facebook is always a day or two OLD https://bugs.launchpad.net/bugs/572011 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 550061] Re: Plymouth not showing on shutdown/restart
which version of plymouth do you have? You can check this by running in a terminal the command apt-cache policy plymouth On 26/04/2010, Claudio Moretti wrote: > On 26/04/2010, Guy Van Sanden wrote: > > Yes, it shows at boot but only the purple bar at the bottom on shutdown > > > > > > -- > > Plymouth not showing on shutdown/restart > > https://bugs.launchpad.net/bugs/550061 > > You received this bug notification because you are a direct subscriber > > of the bug. > > > > Status in “plymouth” package in Ubuntu: Incomplete > > > > Bug description: > > Binary package hint: plymouth > > > > Plymouth is showing at boot (though in 640x480 mode), but at shutdown I > only see a purple bar at the bottom of the screen, the rest is black and > there is some flickering inbetween. > > > > ProblemType: Bug > > Architecture: amd64 > > Date: Sun Mar 28 07:59:03 2010 > > DistroRelease: Ubuntu 10.04 > > MachineType: Dell Inc. Precision M4400 > > NonfreeKernelModules: nvidia > > Package: plymouth 0.8.1-1ubuntu1 > > PccardctlIdent: > > Socket 0: > >no product info available > > PccardctlStatus: > > Socket 0: > >no card > > ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-17-generic > root=/dev/mapper/hostname-root ro quiet splash > > ProcEnviron: > > LANGUAGE=en_DK:en_GB:en > > LC_CTYPE=C > > PATH=(custom, user) > > LANG=en_US.UTF-8 > > SHELL=/usr/bin/zsh > > ProcFB: > > 0 EFI VGA > > 1 VGA16 VGA > > ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 > > SourcePackage: plymouth > > Uname: Linux 2.6.32-17-generic x86_64 > > dmi.bios.date: 10/30/2009 > > dmi.bios.vendor: Dell Inc. > > dmi.bios.version: A18 > > dmi.board.vendor: Dell Inc. > > dmi.chassis.type: 8 > > dmi.chassis.vendor: Dell Inc. > > dmi.modalias: > dmi:bvnDellInc.:bvrA18:bd10/30/2009:svnDellInc.:pnPrecisionM4400:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: > > dmi.product.name: Precision M4400 > > dmi.sys.vendor: Dell Inc. > > > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/550061/+subscribe > > > -- Plymouth not showing on shutdown/restart https://bugs.launchpad.net/bugs/550061 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 550061] Re: Plymouth not showing on shutdown/restart
On 26/04/2010, Guy Van Sanden wrote: > Yes, it shows at boot but only the purple bar at the bottom on shutdown > > > -- > Plymouth not showing on shutdown/restart > https://bugs.launchpad.net/bugs/550061 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “plymouth” package in Ubuntu: Incomplete > > Bug description: > Binary package hint: plymouth > > Plymouth is showing at boot (though in 640x480 mode), but at shutdown I only > see a purple bar at the bottom of the screen, the rest is black and there is > some flickering inbetween. > > ProblemType: Bug > Architecture: amd64 > Date: Sun Mar 28 07:59:03 2010 > DistroRelease: Ubuntu 10.04 > MachineType: Dell Inc. Precision M4400 > NonfreeKernelModules: nvidia > Package: plymouth 0.8.1-1ubuntu1 > PccardctlIdent: > Socket 0: >no product info available > PccardctlStatus: > Socket 0: >no card > ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-17-generic > root=/dev/mapper/hostname-root ro quiet splash > ProcEnviron: > LANGUAGE=en_DK:en_GB:en > LC_CTYPE=C > PATH=(custom, user) > LANG=en_US.UTF-8 > SHELL=/usr/bin/zsh > ProcFB: > 0 EFI VGA > 1 VGA16 VGA > ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 > SourcePackage: plymouth > Uname: Linux 2.6.32-17-generic x86_64 > dmi.bios.date: 10/30/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A18 > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA18:bd10/30/2009:svnDellInc.:pnPrecisionM4400:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Precision M4400 > dmi.sys.vendor: Dell Inc. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/550061/+subscribe > -- Plymouth not showing on shutdown/restart https://bugs.launchpad.net/bugs/550061 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 550061] Re: Plymouth not showing on shutdown/restart
Is this happening yet? ** Changed in: plymouth (Ubuntu) Status: New => Incomplete -- Plymouth not showing on shutdown/restart https://bugs.launchpad.net/bugs/550061 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 545536] Re: Not able to boot
I thought I had solved; however, today it represented in the form of forcing me to Ctrl+Alt+Del it 5 or 6 times before having my system booted. It always sticks at Waiting for /home [SM] I'm updating now, and plymouth is one of the provided updates, so it _may_ be fixed now, but I don't really know and I don't want to reboot as I have a working system... This said, I'll reboot as soon as I finish doing my stuff and then I can tell if it was fixed or not On Sat, Mar 27, 2010 at 05:32, goldfish2 wrote: > Claudio Moretti, even if the original poster doesn't have encrypted > volumes, I have encrypted volumes and am having this errror... what is > the solution that you found? Thanks. > > -- > Not able to boot > https://bugs.launchpad.net/bugs/545536 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: Incomplete > > Bug description: > I upgraded to current beta version of ubuntu 10.4. today. all went fine in > the ugprade process, but when I tried to boot, the system will hang up in > the same position. Tried this with all kernel versions and (recovery) boot > options. > > the system will start to boot and than report: > init: ureadahead - other main process (891)terminated with status 4 > init: ureadahead - other main process (896) terminated with status 4 > init: ureadahead - other main process (901)terminated with status 4 > init: ureadahead - other main process (904)terminated with status 4 > > and below somethink like > waiting for WD My Book > > no matter what you press, the system will not continue. I managed to get to > a command line, and was able to run some basic commands. > > I am currently in Windows and are not able to get any data from Ubuntu with > some logs. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+bug/545536/+subscribe > -- Not able to boot https://bugs.launchpad.net/bugs/545536 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 545536] Re: Not able to boot
This leads me to a question: do you use encrypted volumes? I had the same problem (even if it's now solved) -- Not able to boot https://bugs.launchpad.net/bugs/545536 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 545536] Re: Not able to boot - ureadahead other main process terminated with status 4
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 545536 This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance! When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: ureadahead (Ubuntu) Status: New => Incomplete -- Not able to boot - ureadahead other main process terminated with status 4 https://bugs.launchpad.net/bugs/545536 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 525295] Re: Lucid indicator icons are not shown. Displays the "unknown icon" instead
bug #543592 is a duplicate of bug #542365, so you need to edit the duplicate status of the first and then mark the second as a duplicate. But I don't understand why you think #542365 is a duplicate of this, as it is related to the volume applet, not to the volume icon -- Lucid indicator icons are not shown. Displays the "unknown icon" instead https://bugs.launchpad.net/bugs/525295 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 379976] Re: Karmic does not Shutdown or Reboot
As I'm not a developer, nor I have this problem anymore, I cannot help more than asking you to provide details about your issue (which I've already done) and waiting to see if a developer or someone who knows what this issue might be related to, provides an answer or a workaround. I can only ask you to provide your /var/log/dmesg /var/log/dmesg. /var/log/syslog /var/log/syslog.1 files, to see if there is a hint about what process is preventing shutdown and reboot to complete. On Wed, Mar 17, 2010 at 18:47, mf wrote: > any idea's anyone? > > -- > Karmic does not Shutdown or Reboot > https://bugs.launchpad.net/bugs/379976 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: Confirmed > > Bug description: > Shutting down or restarting Karmic result in a blank black screen with a > flashing cursor in the top left. No errors or messages. Using the wireless > kill switch beforehand fixes this. > > Karmic alpha 1 > Kernel 2.6.30-5-generic (AMD64) > Intel 3945 > Dell Precision M90 > > ProblemType: Bug > Architecture: amd64 > DistroRelease: Ubuntu 9.04 > HibernationDevice: RESUME=UUID=a5076806-3e1d-4a1f-ade4-5f31c2b78672 > MachineType: Dell Inc. Precision M90 > NonfreeKernelModules: nvidia > Package: linux-image-2.6.28-11-generic 2.6.28-11.42 > ProcCmdLine: root=UUID=40597855-d643-4b8e-bc52-a4795cd63a20 ro quiet splash > ProcEnviron: > LANG=en_GB.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.28-11.42-generic > SourcePackage: linux > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379976/+subscribe > -- Karmic does not Shutdown or Reboot https://bugs.launchpad.net/bugs/379976 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 529230] Re: X server crashes when enter key is pressed
Henning, #532047 has been fixed, as they say; /usr/share/initramfs-tools/conf-hooks.d/plymouth does not exist in my system with plymouth 0.8.0~-14 -- X server crashes when enter key is pressed https://bugs.launchpad.net/bugs/529230 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 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
Bug behaviour: pressing 2 or Enter causes gdm restart. On Sun, Mar 14, 2010 at 18:29, pablomme wrote: > What I just described is covered by bug #538214, by the way. > > -- > Plymouth text-mode splash causes X to crash on first run due to shared tty7 > https://bugs.launchpad.net/bugs/532047 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in X.Org X server: Invalid > Status in “plymouth” package in Ubuntu: Fix Released > Status in “xorg-server” package in Ubuntu: Invalid > > Bug description: > Binary package hint: plymouth > > Lucid adopted the Plymouth graphical splash service that uses the Kernel > Mode Setting (KMS) facilities to provide a flicker-free graphical splash > during start-up. For older video chipsets and drivers (e.g. intel i815) that > *do not* support KMS plymouth falls back to using a text console (using the > text plugin). It attaches to tty7 and outputs Linux terminfo control codes > to draw a colour progress-bar at the bottom of the display. > > There is an unfortunate interaction between plymouth and X. X also uses > tty7. When the X/GDM log-in screen appears for the first time plymouth is > still running. A script triggers a quit message to the plymouth daemon. It > seems that plymouth is waiting for either the "2" key or "Enter" key to be > pressed, whereupon a SIGQUIT (signal 3) is sent to tty7. This causes both > plymouth *and* X to terminate. > > So, if a password contains "2" or the user logs in by pressing "Enter" > after typing their password, the user experience is that X 'crashes' > (however, gdb reveals that X receives SIGQUIT). > > Some stray plymouth control codes can be witnessed on tty7 if X is stopped > and tty7 console is on-screen. > > Upstart (/sbin/init) then restarts gdm (which launches X) and the second > session performs correctly. > > *** A temporary workaround is to disable the plymouth-splash upstart job > *** > > sudo mv /etc/init/plymouth-splash.conf > /etc/init/plymouth-splash.conf.disabled > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/xorg-server/+bug/532047/+subscribe > -- Plymouth text-mode splash causes X to crash on first run due to shared tty7 https://bugs.launchpad.net/bugs/532047 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 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
Still experiencing it: r...@jarvis:~# apt-cache policy plymouth plymouth: Installato: 0.8.0~-14 Candidato: 0.8.0~-14 Tabella versione: *** 0.8.0~-14 0 500 http://archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status r...@jarvis:~# apt-cache policy plymouth-x11 plymouth-x11: Installato: 0.8.0~-14 Candidato: 0.8.0~-14 Tabella versione: *** 0.8.0~-14 0 500 http://archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status r...@jarvis:~# apt-cache policy libplymouth2 libplymouth2: Installato: 0.8.0~-14 Candidato: 0.8.0~-14 Tabella versione: *** 0.8.0~-14 0 500 http://archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status r...@jarvis:~# apt-cache policy mountall mountall: Installato: 2.8 Candidato: 2.8 Tabella versione: *** 2.8 0 500 http://archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status r...@jarvis:~# uname -a Linux Jarvis 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux -- Plymouth text-mode splash causes X to crash on first run due to shared tty7 https://bugs.launchpad.net/bugs/532047 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 533773] Re: NVIDIA driver does not load on startup - low-graphics mode
The Nvidia installer produces a kernel module only for the kernel you are running at the time of execution; if you install linux-headers-2.6.31-19-generic, boot the 2.6.31-19 kernel and run the nvidia installer, the module should be built and the system become usable; however, as you said, you con't need it anymore. My personal advise, although, is to install the nvidia-current package, which installs the driver from the repositories (avoiding the need of the manual sh) and adds a hook that builds th module for every installed kernel (http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support). > On Sat, Mar 13, 2010 at 20:22, Toto wrote: > I installed "build-essential", there was no more the error window, but the > screen blinked and only command line (no graphic mode) was available. > Then I re-installed the NVIDIA driver, using this command line: >sudo sh ./NVIDIA-Linux-x86_64-190.53-pkg2.run > and >sudo kdm start > and then it was possible to enter into graphic mode. > > Now I can start a graphic session with "Ubuntu, Linux > 2.6.31-20-generic", but no more with "Ubuntu, Linux 2.6.31-19-generic": > the screen blinks and only command line (no graphic mode) is available. > > The output of > apt-cache policy linux-headers-2.6.31-19-generic > is: > linux-headers-2.6.31-19-generic: > Installé : (aucun) > Candidat : 2.6.31-19.56 > Table de version : > 2.6.31-19.56 0 > 500 http://mc.archive.ubuntu.com karmic-updates/main Packages > 500 http://security.ubuntu.com karmic-security/main Packages > W: Duplicate sources.list entry http://ppa.launchpad.net karmic/main > Packages > (/var/lib/apt/lists/ppa.launchpad.net_lcid-fire_areca_ubuntu_dists_karmic_main_binary-amd64_Packages) > > The output of > apt-cache policy build-essential > is: > build-essential: >Installé : 11.4 >Candidat : 11.4 > Table de version : > *** 11.4 0 > 500 http://mc.archive.ubuntu.com karmic/main Packages > 100 /var/lib/dpkg/status > W: Duplicate sources.list entry http://ppa.launchpad.net karmic/main > Packages > (/var/lib/apt/lists/ppa.launchpad.net_lcid-fire_areca_ubuntu_dists_karmic_main_binary-amd64_Packages) > > However, since "Linux 2.6.31-20-generic" seems to run well, I do not > need anymore "Linux 2.6.31-19-generic". > > -- > NVIDIA driver does not load on startup - low-graphics mode > https://bugs.launchpad.net/bugs/533773 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: Invalid > > Bug description: > Ubuntu release: Ubuntu 9.10 Karmic Koala 64 bit - Kubuntu - "Ubuntu, Linux > 2.6.31-20-generic" > > What was expected to happen: full graphic mode on start-up after having > chosen the kernel version "Ubuntu, Linux 2.6.31-20-generic" > > What happened instead: the following window appeared: > "Ubuntu is running in low-graphics mode. >The following error was encountered. You may need to update your > configuration to solve this. > (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your > system's kernel log for additional error messages. > (EE) Failed to load module "nvidia" (module-specific error, 0) > (EE) No drivers available" > > Additional informations: > - this bug appeared on first run of version "Ubuntu, Linux > 2.6.31-20-generic" and at each following run; > - running back the previous version "Ubuntu, Linux 2.6.31-19-generic" did > not induce this bug; full graphic mode and KDE desktop appeared as expected > and the system was fully operational; > - graphic card: NVIDIA GeForce GTX 280M > - graphic card driver: NVIDIA 190.53 (NVIDIA-Linux-x86_64-190.53-pk2.run > file downloaded from NVIDIA internet support site); again, no issue when > running this driver with the previous versions "Ubuntu, Linux > 2.6.31-19-generic" or lower; > - PC: Clevo Notebook W870CU > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+bug/533773/+subscribe > -- NVIDIA driver does not load on startup - low-graphics mode https://bugs.launchpad.net/bugs/533773 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 533773] Re: NVIDIA driver does not load on startup - low-graphics mode
** Changed in: ubuntu Status: Incomplete => Invalid -- NVIDIA driver does not load on startup - low-graphics mode https://bugs.launchpad.net/bugs/533773 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 379976] Re: Karmic does not Shutdown or Reboot
I am not experiencing this issue since I upgraded to 2.6.31-8. The fix was released 4 months ago, so it should be fixed now. Is your system fully upgraded? Can you please provide details about your system? (Brand, model, the output of the "lspci", "lsmod" and "dmesg" commands) On Wed, Mar 10, 2010 at 19:00, mf wrote: > what fix? i'm running 2.6.32-16-386 and i have the problem. I have > spent 3 months trying to fix this and i'm at wits end. > > It really is a serious problem for people with laptops and netbooks!! > > Could somebody please link me to the solution? > > -- > Karmic does not Shutdown or Reboot > https://bugs.launchpad.net/bugs/379976 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: Confirmed > > Bug description: > Shutting down or restarting Karmic result in a blank black screen with a > flashing cursor in the top left. No errors or messages. Using the wireless > kill switch beforehand fixes this. > > Karmic alpha 1 > Kernel 2.6.30-5-generic (AMD64) > Intel 3945 > Dell Precision M90 > > ProblemType: Bug > Architecture: amd64 > DistroRelease: Ubuntu 9.04 > HibernationDevice: RESUME=UUID=a5076806-3e1d-4a1f-ade4-5f31c2b78672 > MachineType: Dell Inc. Precision M90 > NonfreeKernelModules: nvidia > Package: linux-image-2.6.28-11-generic 2.6.28-11.42 > ProcCmdLine: root=UUID=40597855-d643-4b8e-bc52-a4795cd63a20 ro quiet splash > ProcEnviron: > LANG=en_GB.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.28-11.42-generic > SourcePackage: linux > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379976/+subscribe > -- Karmic does not Shutdown or Reboot https://bugs.launchpad.net/bugs/379976 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 395299] Re: gdm 2.26 has no graphical configuration tool
Try purging the gdm2 configuration tool via sudo apt-get purge packagename or, if it doesn't work sudo dpkg -P packagename If you installed it from the repos or a .deb package, it should remove it. Then do a sudo apt-get --purge autoremove and sudo apt-get clean which will remove all packages that have been downloaded from apt (the apt package cache) and, finally execute sudo apt-get --reinstall install gdm If the problem was the gdm2 manager it should be gone. in EVERY step of this procedure, particularly at the autoremove, pay attention to the packages that are removed. if you notice some programs and/or libraries you think must stay there, or see a huge list of packages that are going to be removed, abort; your system shouldn't be affected, if you do so. On Tue, Mar 9, 2010 at 22:15, David Robert Lewis wrote: > All this security is a real hassle. Just as I was beginning to love the > new GDM, after discovering how to change the background, I foolishly > installed some tool claiming to be the answer to GDM2 configuration. > Result is I have a frozen GDM greeter, which refuses to show user > password entry box. It just freezes except for the disability panel. I > have tried reinstalling several times. I have also tried deleting the > usr/share/gdm folder. To no avail. About to tear out the remains of my > hair over this. Please, some solution for reinstalling GDM and bypassing > all the aweful Windows-like security. > > -- > gdm 2.26 has no graphical configuration tool > https://bugs.launchpad.net/bugs/395299 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in GDM: The Gnome Display Manager: New > Status in “gdm” package in Ubuntu: Fix Released > Status in “gdm” source package in Karmic: Fix Released > > Bug description: > Binary package hint: gdm > > In Karmic the Login Window Preferences option from the GNOME System -> > Preferences menu is missing. I'm no longer able to configure gdm > graphically. Something I was able to do until recently and in Jaunty. > > The new gdm : > - discussion have started during the hardy uds 1.5 year ago > - the new gdm has been accepted upstream by GNOME and used for over a year > in several other distributions > - the ubuntu team decided to wait on the change because of the known issues > - the new version was available since jaunty in the ubuntu-desktop ppa and > call for testing have been made > - the change has been decided this cycle because karmic had technologies > changes in view of the lts coming next cycle, it's better to use recent and > maintainer codebases there > - the canonical desktop team spent time this cycle writing a gdmsetup tool > and fixing several issues in the new gdm version > It's not perfect yet but is expected to be improved. > Thanks for your patience! > - > The changes are due to an upstream [Gnome] update , which was blocked in > Ubuntu for 3 cycles . > Any further discussions regarding lack of features can be discussed > > https://bugzilla.gnome.org/show_bug.cgi?id=587750 or users can open new > bugs regarding the missing features. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/gdm/+bug/395299/+subscribe > -- gdm 2.26 has no graphical configuration tool https://bugs.launchpad.net/bugs/395299 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 533773] Re: NVIDIA driver does not load on startup - low-graphics mode
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information. Please run the following command which will attach necessary information: apport-collect 533773 Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python- launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options): First run the following commands: 1) uname -a > uname-a.log 2) dmesg > dmesg.log 3) sudo lspci -vvnn > lspci-vvnn.log 4) cat /proc/version_signature > version.log then attach the files separately to the bug report (not pasted into comments or tar/zip-ed). However, this seems to be an issue with the driver module not being built. Please, copy and paste the output of apt-cache policy linux-headers-2.6.31-20-generic and apt-cache policy build-essential Thanks! ** Changed in: ubuntu Status: New => Incomplete -- NVIDIA driver does not load on startup - low-graphics mode https://bugs.launchpad.net/bugs/533773 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 517293] Re: transmission crashed with signal 5 in XListPixmapFormats()
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- transmission crashed with signal 5 in XListPixmapFormats() https://bugs.launchpad.net/bugs/517293 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 519213] Re: X restarts once if '2' key is pressed when gdm password field has focus
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- X restarts once if '2' key is pressed when gdm password field has focus https://bugs.launchpad.net/bugs/519213 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 519410] Re: Lucid freezes at gdm login
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- Lucid freezes at gdm login https://bugs.launchpad.net/bugs/519410 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 522554] Re: Logged out when typing 2 or @
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- Logged out when typing 2 or @ https://bugs.launchpad.net/bugs/522554 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 522692] Re: Pressing key causes gdm to restart on first boot
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 I am marking this bug as a duplicate of #532047, even if this was opened before, as this bug importance has not yet been decided and in the other one there's a solution WIP. This is unusual but not unique (happened to me once), so please don't complain =) ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- Pressing key causes gdm to restart on first boot https://bugs.launchpad.net/bugs/522692 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 525386] Re: GDM restarts once after boot in Lucid
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- GDM restarts once after boot in Lucid https://bugs.launchpad.net/bugs/525386 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 528076] Re: Entering specific string(s) of characters causes X to restart
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- Entering specific string(s) of characters causes X to restart https://bugs.launchpad.net/bugs/528076 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 528830] Re: Must log in twice to gdm in Lucid
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- Must log in twice to gdm in Lucid https://bugs.launchpad.net/bugs/528830 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 529999] Re: Login screen restarts when "2" is typed
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- Login screen restarts when "2" is typed https://bugs.launchpad.net/bugs/52 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 531534] Re: gdm login restarts the first time
*** This bug is a duplicate of bug 532047 *** https://bugs.launchpad.net/bugs/532047 ** This bug is no longer a duplicate of bug 522692 Pressing key causes gdm to restart on first boot ** This bug has been marked a duplicate of bug 532047 Plymouth text-mode splash causes X to crash on first run due to shared tty7 -- gdm login restarts the first time https://bugs.launchpad.net/bugs/531534 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 522692] Re: Pressing key causes gdm to restart on first boot
I can reproduce it pressing 2 on an Italian QWERTY, so I think it's definitely a 2 :) On Sat, Mar 6, 2010 at 14:07, Martin Karlsson wrote: > Does that character happen to be a 2 or an @? :) There's a related bug > #522554 where that happens, it's marked as a duplicate of this bug. > > -- > Pressing key causes gdm to restart on first boot > https://bugs.launchpad.net/bugs/522692 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “plymouth” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: plymouth > > Pressing the enter key sometime during the first X session after boot will > kill X and gdm will restart. Subsequent logins will work fine. On > investigation, this occurs because X is being sent SIGQUIT (see > http://paste.ubuntu.com/382615/ - using trace-signal.ko). After X is > killed it starts on a different VT and will no longer be sent SIGQUIT when > pressing enter. > > It seems that other distributions are working around this by starting X on > a different VT to plymouth. > > Original description: > Pressing the enter key causes the whole system to freeze. The system still > respond to ssh. > > It does not happen on every boot, but a visible screen corruption in the > top left side of the screen is a symptom that the crash will happen in that > session. > > Note: This is not a duplicate of bug #516412 as stated by Steve Langasek in > the comment #78 there. > > WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K > fixes the problem until the next reboot. Some also may want to remove the > plymouth package until this bug is fixed. > > ProblemType: Bug > Architecture: i386 > CheckboxSubmission: 56f6196d6c59b6b05a94181cc3955a09 > CheckboxSystem: c4d84cd56dc0e1c868ed7fe87c94fd31 > Date: Tue Feb 16 16:15:36 2010 > DistroRelease: Ubuntu 10.04 > Package: plymouth 0.8.0~-10 > ProcEnviron: > LANGUAGE=en_US.UTF-8 > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.32-9.13-generic > SourcePackage: plymouth > Uname: Linux 2.6.32-9-generic i686 > > --- > Architecture: i386 > CheckboxSubmission: 56f6196d6c59b6b05a94181cc3955a09 > CheckboxSystem: c4d84cd56dc0e1c868ed7fe87c94fd31 > DistroRelease: Ubuntu 10.04 > MachineType: LG Electronics E200-A.CP29B > Package: plymouth 0.8.0~-10ubuntu1 > PackageArchitecture: i386 > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-9-generic > root=UUID=f1e83727-9d0c-4969-8f3c-f5dd6fa01dbc ro quiet splash > ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.32-9-generic > root=UUID=f1e83727-9d0c-4969-8f3c-f5dd6fa01dbc ro quiet splash > ProcEnviron: > LANGUAGE=en_US.UTF-8 > PATH=(custom, no user) > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcFB: 0 VGA16 VGA > ProcVersionSignature: Ubuntu 2.6.32-9.13-generic > Tags: lucid > Uname: Linux 2.6.32-9-generic i686 > UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare > dmi.bios.date: 10/02/2007 > dmi.bios.vendor: Phoenix Technologies LTD > dmi.bios.version: ELBRSF0C > dmi.board.name: Lhotse-II > dmi.board.vendor: LG Electronics Inc. > dmi.board.version: Rev0.4b > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 1 > dmi.chassis.vendor: LG Electronics Inc. > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnPhoenixTechnologiesLTD:bvrELBRSF0C:bd10/02/2007:svnLGElectronics:pnE200-A.CP29B:pvr0100:rvnLGElectronicsInc.:rnLhotse-II:rvrRev0.4b:cvnLGElectronicsInc.:ct1:cvrN/A: > dmi.product.name: E200-A.CP29B > dmi.product.version: 0100 > dmi.sys.vendor: LG Electronics > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/522692/+subscribe > -- Pressing key causes gdm to restart on first boot https://bugs.launchpad.net/bugs/522692 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 531265] Re: Linux 2.6.32-15-generic does not correctly handle permissions
I understand this, but cannot understand what does the read permission on a folder implies. Can you explain this to me? =) (Or give me the posix definition you were reading, which is definitely faster) Thanks! On Fri, Mar 5, 2010 at 02:26, Andy Whitcroft wrote: > @Claudio -- the execute permission bit on a directory is the 'traversal' > bit, without this bit a user is not permitted to pass through this > directory to open a file even if the file is readable. That applied to > chdir() and getdents() equally, preventing a cd into the directory. > This behaviour seems as expected from the posix definition to my > reading. > > ** Changed in: linux (Ubuntu) > Status: New => Invalid > > ** Changed in: linux (Ubuntu) > Assignee: (unassigned) => Andy Whitcroft (apw) > > -- > Linux 2.6.32-15-generic does not correctly handle permissions > https://bugs.launchpad.net/bugs/531265 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: Invalid > > Bug description: > I cannot cd to a folder not owned by me, without having set the execute > permission on a folder, even if there is the "universe read" one. > I can however edit files that don't have the x permission. > Steps to reproduce: > > 1) Create a folder > 2) chown that folder to another user > 3) chmod it to drwx--x--x (run as root: chmod a-rwx foldername && chmod a+r > foldername) > 4) try to cd into it > > r...@jarvis:~# mkdir test > r...@jarvis:~# chmod a-rwx test && chmod a+r test > r...@jarvis:~# ls -l |grep test > dr--r--r-- 2 rootroot 4096 2010-03-03 12:10 test > > clau...@jarvis:~$ cd test/ > bash: cd: test/: Permesso negato > > = > clau...@jarvis:~$ uname -a > Linux Jarvis 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:23:29 UTC 2010 > x86_64 GNU/Linux > clau...@jarvis:~$ cat /proc/version_signature > Ubuntu 2.6.32-15.22-generic > > ProblemType: Bug > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. > Architecture: amd64 > ArecordDevices: > List of CAPTURE Hardware Devices > card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: claudio1889 F pulseaudio > CRDA: > country 98: >(2402 - 2482 @ 40), (N/A, 20) > Card0.Amixer.info: > Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 21' > Mixer name : 'SigmaTel STAC9205' > Components : 'HDA:838476a0,10280228,00100204 > HDA:14f12c06,14f1000f,0010' > Controls : 19 > Simple ctrls : 11 > Date: Wed Mar 3 12:03:07 2010 > DistroRelease: Ubuntu 10.04 > HibernationDevice: RESUME=UUID=3be917d1-4bb8-4d17-846b-88461c8a74b3 > MachineType: Dell Inc. Vostro 1500 > NonfreeKernelModules: nvidia > Package: linux-image-2.6.32-15-generic 2.6.32-15.22 > ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic > root=/dev/mapper/sda6_crypt ro quiet > ProcEnviron: > LANG=it_IT.utf8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.32-15.22-generic > Regression: No > RelatedPackageVersions: linux-firmware 1.31 > Reproducible: Yes > SourcePackage: linux > TestedUpstream: No > Uname: Linux 2.6.32-15-generic x86_64 > dmi.bios.date: 04/21/2008 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A06 > dmi.board.name: 0WY040 > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Vostro 1500 > dmi.sys.vendor: Dell Inc. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/531265/+subscribe > -- Linux 2.6.32-15-generic does not correctly handle permissions https://bugs.launchpad.net/bugs/531265 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 531265] Re: Linux 2.6.32-15-generic does not correctly handle permissions
** Attachment added: "lspci-vnvn.log" http://launchpadlibrarian.net/40049599/lspci-vnvn.log ** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/40049600/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/40049601/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/40049602/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/40049603/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/40049604/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/40049605/Card0.Codecs.codec.1.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/40049606/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/40049607/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/40049608/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/40049609/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/40049610/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/40049611/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/40049612/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/40049613/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/40049614/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/40049615/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/40049616/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/40049617/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/40049618/WifiSyslog.txt -- Linux 2.6.32-15-generic does not correctly handle permissions https://bugs.launchpad.net/bugs/531265 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 531265] [NEW] Linux 2.6.32-15-generic does not correctly handle permissions
Public bug reported: I cannot cd to a folder not owned by me, without having set the execute permission on a folder, even if there is the "universe read" one. I can however edit files that don't have the x permission. Steps to reproduce: 1) Create a folder 2) chown that folder to another user 3) chmod it to drwx--x--x (run as root: chmod a-rwx foldername && chmod a+r foldername) 4) try to cd into it r...@jarvis:~# mkdir test r...@jarvis:~# chmod a-rwx test && chmod a+r test r...@jarvis:~# ls -l |grep test dr--r--r-- 2 rootroot 4096 2010-03-03 12:10 test clau...@jarvis:~$ cd test/ bash: cd: test/: Permesso negato = clau...@jarvis:~$ uname -a Linux Jarvis 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:23:29 UTC 2010 x86_64 GNU/Linux clau...@jarvis:~$ cat /proc/version_signature Ubuntu 2.6.32-15.22-generic ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claudio1889 F pulseaudio CRDA: country 98: (2402 - 2482 @ 40), (N/A, 20) Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 21' Mixer name : 'SigmaTel STAC9205' Components : 'HDA:838476a0,10280228,00100204 HDA:14f12c06,14f1000f,0010' Controls : 19 Simple ctrls : 11 Date: Wed Mar 3 12:03:07 2010 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=3be917d1-4bb8-4d17-846b-88461c8a74b3 MachineType: Dell Inc. Vostro 1500 NonfreeKernelModules: nvidia Package: linux-image-2.6.32-15-generic 2.6.32-15.22 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic root=/dev/mapper/sda6_crypt ro quiet ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic Regression: No RelatedPackageVersions: linux-firmware 1.31 Reproducible: Yes SourcePackage: linux TestedUpstream: No Uname: Linux 2.6.32-15-generic x86_64 dmi.bios.date: 04/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid needs-upstream-testing -- Linux 2.6.32-15-generic does not correctly handle permissions https://bugs.launchpad.net/bugs/531265 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 516412] Re: Pressing causes X to freeze
Even if I agree with you on the language matter, I must point out a thing: r...@jarvis:~# apt-get remove plymouth Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti: linux-backports-modules-nouveau-2.6.32-14-generic db4.6-util libbttracker0 libbtutil0 libmcrypt4 libapache2-mod-bt libdb4.6 Usare "apt-get autoremove" per rimuoverli. I seguenti pacchetti saranno RIMOSSI: cryptsetup plymouth plymouth-x11 0 aggiornati, 0 installati, 3 da rimuovere e 0 non aggiornati. Dopo quest'operazione, verranno liberati 2269kB di spazio su disco. Continuare [S/n]? n Interrotto. I need cryptsetup and I cannot remove it without being unable to use my system On Wed, Mar 3, 2010 at 00:51, Matthieu Baerts wrote: > I agree with Anthony Hook ! > > > "Most of us are volunteers and this type of behavior is > unacceptable." > > If you don't like Plymouth, simply uninstall it... Or if you didn't like > Ubuntu and its Code of Conduct, there are other solutions ! > > -- > Pressing causes X to freeze > https://bugs.launchpad.net/bugs/516412 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “plymouth” package in Ubuntu: Fix Released > > Bug description: > Binary package hint: plymouth > > I am running ubuntu 10.04 Alpha2 and after last nights updates pressing the > enter key causes the whole system to freeze and I have to hard reboot. > > Only removing Plymouth would allow me to work normally. > > The system still respond to ssh. > > WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K > fixes the problem until the next reboot. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/+subscribe > -- Pressing causes X to freeze https://bugs.launchpad.net/bugs/516412 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 516412] Re: Pressing causes X to freeze
> > Developers should test such a things on different > graphic cards prior to send it to repo > Also, what did you expect from a _development_ release? On Tue, Mar 2, 2010 at 17:29, Sense Hofstede wrote: > burivoy: Please read the previous comments. As the developer indicated > that this specific bug was fixed. There might be other bugs with the > same symptoms, but they are different bugs. Maybe you're using different > hardware than the original reporter. Furthermore, the fact that removing > Plymouth doesn't solve the issue for you is another indication that > you're suffering from a different bug, most likely in GDM. > > About the testing: if you could provide the developers with the hardware > and the time for testing new packages that extensively, then we'd be > happy to do more extensive testing. Otherwise, please consider > reinforcing the testing team, which can use some help as well. > > Please also mind your language. > > -- > Pressing causes X to freeze > https://bugs.launchpad.net/bugs/516412 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “plymouth” package in Ubuntu: Fix Released > > Bug description: > Binary package hint: plymouth > > I am running ubuntu 10.04 Alpha2 and after last nights updates pressing the > enter key causes the whole system to freeze and I have to hard reboot. > > Only removing Plymouth would allow me to work normally. > > The system still respond to ssh. > > WORKAROUND (thanks to Simon Baconnais): kill X by pressing Ctrl+Alt+Print+K > fixes the problem until the next reboot. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/516412/+subscribe > -- Pressing causes X to freeze https://bugs.launchpad.net/bugs/516412 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 526321] Re: System does not booth with last plymouth. SAK needed to unlock it.
I don't know how to verify it, but I can exclude tha last 2 entries as sudo ls -la /dev/.initramfs returns the following: r...@jarvis:/dev/.initramfs# ls -la totale 0 drwxr-xr-x 2 root root 40 2010-02-25 13:14 . drwxr-xr-x 16 root root 3880 2010-02-25 15:50 .. I have also found this: r...@jarvis:/var/log# grep plymouth daemon.log* daemon.log:Feb 22 09:46:28 Jarvis init: plymouth-splash pre-start process (1258) terminated with status 111 daemon.log:Feb 23 10:18:27 Jarvis init: plymouth-splash pre-start process (1222) terminated with status 111 daemon.log:Feb 23 10:33:58 Jarvis init: plymouth main process (332) killed by TERM signal daemon.log:Feb 23 10:35:34 Jarvis init: plymouth main process (381) killed by TERM signal daemon.log:Feb 24 10:15:52 Jarvis init: plymouth main process (360) killed by TERM signal daemon.log:Feb 24 14:12:32 Jarvis init: plymouth main process (347) killed by TERM signal daemon.log:Feb 25 09:20:58 Jarvis init: plymouth main process (340) killed by TERM signal daemon.log:Feb 25 13:14:27 Jarvis init: plymouth main process (383) killed by TERM signal daemon.log.1:Feb 17 11:38:04 Jarvis init: plymouth main process (341) killed by TERM signal daemon.log.1:Feb 17 12:09:24 Jarvis init: plymouth-splash pre-start process (1549) terminated with status 111 daemon.log.1:Feb 18 09:31:25 Jarvis init: plymouth-splash pre-start process (1390) terminated with status 111 daemon.log.1:Feb 19 11:47:54 Jarvis init: plymouth-splash pre-start process (1710) terminated with status 111 daemon.log.1:Feb 19 20:04:04 Jarvis init: plymouth-splash pre-start process (1571) terminated with status 111 daemon.log.1:Feb 20 11:26:22 Jarvis init: plymouth-splash pre-start process (1499) terminated with status 111 daemon.log.1:Feb 20 17:22:23 Jarvis init: plymouth-splash pre-start process (1552) terminated with status 111 daemon.log.1:Feb 21 09:57:29 Jarvis init: plymouth-splash pre-start process (1535) terminated with status 111 Please let me know if there's something else I can provide. On Thu, Feb 25, 2010 at 11:13, Steve Langasek wrote: > Yes, plymouth should fall back to the text plugin when not given > 'splash', but you may have found a problem that's specific to the text > plugin so I think we want to verify whether it happens when using > splash. > > Also, if plymouth is running in the initramfs like it should be, it > doesn't matter what start condition the upstart job lists, because the > process should already be running. So there are several possible causes > here, none of which are reproducible for me: > > - plymouth is not present in the initramfs > - plymouth is failing to start in the initramfs and cryptsetup is falling > back to direct prompting for decrypting the root filesystem > - plymouth is starting, but exiting abnormally after decrypting the root > filesystem > - plymouth is failing to write out the PID file to > /dev/.initramfs/plymouth.pid > - the PID file is getting written, but isn't being transferred correctly > when chrooting to the real filesystem > - the PID file is getting written, but upstart isn't picking it up > properly > > Perhaps there's something you're seeing that suggests which of these is > taking place, so we can narrow the search. > > -- > System does not booth with last plymouth. SAK needed to unlock it. > https://bugs.launchpad.net/bugs/526321 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “plymouth” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: plymouth > > With plymouth 0.8.0~-10ubuntu1 my system does not boot. It hangs up after > running initramfs-tools/scripts/init-bottom. > Replacing the configuration file with the one that was in 0.8.0~-7 solved > this. > Seems like plymouth does not correctly handle (in init-bottom) the > "post-start exec /bin/plymouth --show-splash " line, or that the missing > "start on (starting mountall" tries to execute plymouth before mountall > causing the system to hang. > > ProblemType: Bug > Architecture: amd64 > Date: Tue Feb 23 10:39:39 2010 > DistroRelease: Ubuntu 10.04 > MachineType: Dell Inc. Vostro 1500 > NonfreeKernelModules: nvidia > Package: plymouth 0.8.0~-10ubuntu1 > ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-14-generic > root=/dev/mapper/sda6_crypt ro quiet > ProcEnviron: > PATH=(custom, no user) > LANG=it_IT.utf8 > SHELL=/bin/bash > ProcFB: 0 VGA16 VGA > ProcVersionSignature: Ubuntu 2.6.32-14.20-generic > SourcePackage: plymouth > Uname: Linux 2.6.32-14-generic x86_64 > dmi.bios.date: 04/21/2008 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A06 > dmi.board.name: 0WY040 > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Vostro 1500 > dmi.sys.vendor: Dell Inc. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/plymouth
[Bug 526321] Re: System does not booth with last plymouth. SAK needed to unlock it.
I'm using cryptsetup 2:1.1.0~rc2-1ubuntu12 to unlock the root filesystem (sda6_crypt) and the home filesystem (sda7_crypt) that is unlocked with a keyfile located into the root fs. Here's my /etc/crypttab sda5_crypt /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap sda6_crypt /dev/disk/by-uuid/9fb5d009-5509-4886-9324-b43d9fd0d161 none luks sda7_crypt /dev/disk/by-uuid/5402c06c-196d-4d97-a3da-ec45ff103ac0 /etc/crypt.key luks I don't really know why I'm booting without the "splash" option, I can only think I don't remember having removed it from /etc/default/grub. Should I put it there? I thought that without the splash option plymouth would fallback to the text theme (if there is one) r...@jarvis:~# plymouth-set-default-theme --list details fade-in glow script solar spinfinity text ubuntu-logo Isn't the "script" one? The only thing I want to clearly point out is that before "patching" the plymouth.conf file my system did not boot. It forced me to Alt+SysRq+K it and drop to a root shell prompt. So I understand that you - a developer - knows that the post-start command is wrong, but now my system boots quite as fast as it did with 0.8.0-~8 (later versions did not boot) so I think about what may be wrong with it. ** Changed in: plymouth (Ubuntu) Status: Incomplete => Confirmed -- System does not booth with last plymouth. SAK needed to unlock it. https://bugs.launchpad.net/bugs/526321 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
