[Bug 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time
What should be done if everything in post #2 is set as directed, but on the following step...: glxgears -info |grep NVIDIA ...the following is returned?: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 31 Current serial number in output stream: 32 NOTE: The workaround provided in post #2 above did in fact solve this issue for a few months on my setup until this morning when this problem started happening again. My computers Specs: CPU: Two Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz Mem: 64GB OS: Xubuntu 18.04.2 LTS Graphics: NVIDIA Quadro P6000 Software & Updates panel: [Ubuntu Software Tab]: (The following are checked) * Canonical-supported free and open-source software (main) * Community-maintained free and open-source software (universe) * Proprietary drivers for devices (restricted) * Software restricted by copyright or legal issues (multiverse) [Additional Drivers Tab]: (The following graphics driver is in use) * Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested) If I'm remembering correctly this setup is currently utalizing some of the functionality provided by the proprietary drivers that can not be provided by the more generic Noveau driver. I can't quite remember what this is at the moment but I would prefer to stick with the proprietary driver if at all possible while solving this problem. Please let me know if there are any other logs or information that I might be able to report in order to help verify or narrow down what is causing this issue to re-occur after the fix provided in step #2 has been applied. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757202 Title: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640678] [NEW] Error in `/usr/share/doc-base/gegl', line 12: all `Format' sections are invalid.
Public bug reported: System specs: OS: Xubuntu 16.04 Xenial x86_64 Kernel: 4.4.0-45-generic libgegl-doc installed version: 1:0.3.11~0-0x0~ppa~363b1c9 Description of problem: Received a message to perform a system update. (Note: this was with a clean and updated apt-cache). Elected to let the GUI perform the update. What was expected was a clean update, but an error message was displayed at some point instead. After viewing /var/log/apt/term.log, the following error was revealed. Error message begins: Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... Error in `/usr/share/doc-base/gegl', line 12: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. Registering documents with scrollkeeper... Error message ends: Suggested action: install-docs --verbose --check /usr/share/doc-base/gegl Results Begins --- Warning in `/usr/share/doc-base/gegl', line 12: file `/usr/share/doc/libgegl-doc/api.html' does not exist. Error in `/usr/share/doc-base/gegl', line 12: all `Format' sections are invalid. /usr/share/doc-base/gegl: Fatal error found, the file won't be registered. Results End 1st Implied action: (check the file) cat /usr/share/doc/doc-base/gegl Result Begins Title: Debian gegl Manual Author: gegl upstream authors Abstract: This manual describes what gegl is and how it can be used to manage online manuals on Debian systems. Section: Graphics Format: HTML Index: /usr/share/doc/libgegl-doc/api.html Files: /usr/share/doc/libgegl-doc/gegl*.html /usr/share/doc/libgegl-doc/operations.html Result Ends Note: 1.) Line 12 is the last line in the results shown above. 2.) The error also mentions that the "Format" section is invalid. 2nd Implied action: (check the referenced directory for file existence). ls -al /usr/share/doc/libgegl-doc/ Result Begins drwxr-xr-x2 root root 4096 Nov 9 20:19 . drwxr-xr-x 4180 root root 139264 Nov 5 13:08 .. -rw-r--r--1 root root 25960 Nov 8 14:51 abyss_policy.html -rw-r--r--1 root root 9306 Nov 8 14:50 brightness-contrast.c.html -rw-r--r--1 root root 26201 Nov 8 14:51 bugzilla.html -rw-r--r--1 root root 27480 Nov 8 14:51 build.html -rw-r--r--1 root root 1124 Nov 8 14:40 changelog.Debian.gz -rw-r--r--1 root root 301094 Nov 8 14:50 class-hierarchy.html -rw-r--r--1 root root 27255 Nov 8 14:51 commandline.html -rw-r--r--1 root root 28099 Nov 8 14:51 contribute.html -rw-r--r--1 root root 2216 Nov 28 2015 copyright -rw-r--r--1 root root 28166 Nov 8 14:51 copyright.html -rw-r--r--1 root root 36621 Nov 8 14:51 development.html -rw-r--r--1 root root 7405 Jul 19 11:17 devhelp.css -rw-r--r--1 root root 26349 Nov 8 14:51 editor.html -rw-r--r--1 root root 26955 Nov 8 14:51 environment.html -rw-r--r--1 root root 27446 Nov 8 14:51 features.html -rw-r--r--1 root root 7816 Jul 19 11:17 gegl.css -rw-r--r--1 root root 4576 Nov 8 14:50 gegl.h.html -rw-r--r--1 root root 4473 Jul 19 11:17 gegl.html -rw-r--r--1 root root 4034 Nov 8 14:50 gegl-operation-area-filter.h.html -rw-r--r--1 root root 3930 Nov 8 14:50 gegl-operation-composer.h.html -rw-r--r--1 root root 3767 Nov 8 14:50 gegl-operation-filter.h.html -rw-r--r--1 root root 18425 Nov 8 14:50 gegl-operation.h.html -rw-r--r--1 root root 4792 Nov 8 14:50 gegl-operation-meta.h.html -rw-r--r--1 root root 5095 Nov 8 14:50 gegl-operation-point-composer.h.html -rw-r--r--1 root root 5392 Nov 8 14:50 gegl-operation-point-filter.h.html -rw-r--r--1 root root 4406 Nov 8 14:50 gegl-operation-point-render.h.html -rw-r--r--1 root root 4000 Nov 8 14:50 gegl-operation-sink.h.html -rw-r--r--1 root root 3772 Nov 8 14:50 gegl-operation-source.h.html -rw-r--r--1 root root 4790 Nov 8 14:50 gegl-operation-temporal.h.html -rw-r--r--1 root root 6071 Nov 8 14:50 gegl-plugin.h.html -rw-r--r--1 root root 26533 Nov 8 14:51 glossary.html -rw-r--r--1 root root 28422 Nov 8 14:51 hello-world.html -rw-r--r--1 root root 29406 Nov 8 14:51 index.html -rw-r--r--1 root root 33323 Nov 8 14:51 journal.html -rw-r--r--1 root root 29175 Nov 8 14:51 operation-api.html -rw-r--r--1 root root 66542 Jul 19 11:17 operations.html -rw-r--r--1 root root 27933 Nov 8 14:51 source-overview.html Result Ends Note: 1.) As can be seen. None of the files mentioned inside "/usr/share/doc-base/gegl" actually exist as referenced. Closing: I hope this report is informative enough to be helpful in some way. ** Affects: gegl (Ubuntu) Importance: Undecided Status: New ** Tags: gegl libgegl-doc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht
[Bug 1640678] Re: Error in `/usr/share/doc-base/gegl', line 12: all `Format' sections are invalid.
CORRECTION: My final note was incorrect. Sorry its late and I'm exhausted. The only file that doesn't exist as referenced in "/usr/share/doc-base/gegl" is "api.html". Hope this clarifies my mistake. My Apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640678 Title: Error in `/usr/share/doc-base/gegl', line 12: all `Format' sections are invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1640678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373254] Re: 14.04LTS upgrades to pip cause object has no attribute 'findall'
>From the forum for the package team responsible for PIP comes the following >comments on this issue: 1st comment dstufft commented on May 26, 2014 Ah I see. So pip itself bundles some software, html5lib being one of those, on various Linux distros they unbundle that software and cause pip to import it normally instead of using it's own bundled copy. What this means is that if you install an incompatible version of one of pip's dependencies into the global Python, then you'll break pip because pip will import that and attempt to use that instead of the correct one installed by apt-get. 2nd comment (a clarification of the 1st comment above) Ivoz commented on Jun 4, 2014 < Python Packaging Authority member> @lrossouw try pip installing packages in a virtualenv or using the --user flag instead of sudo installing them as system packages. The issue seems to be caused by debian's modification of its pip, so we can't address it ourselves. Source for above comments: https://github.com/pypa/pip/issues/1742 I'm including these comments as a record that the dev's in charge of PIP suggested that this issue belongs here. This may not be necessary but it is a record of the events that led here and as such I'm hoping it is at least informative if not helpful to some people. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373254 Title: 14.04LTS upgrades to pip cause object has no attribute 'findall' To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1373254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427401] Re: No new records can be created no matter what settings are used.
A work around for creating a new record is as follows: 1.) Export the current database as a text file by doing the following: 1.a.) File --> Export --> Database to SQL file 1.b.) In the "save as" dialog choose location and file name using the ".txt" file extension to save the file as. 2.) Open the text file saved in step 1.b. above in a text editor and find the line where you would like to insert an record. 3.) Make sure the record being inserted has the same format as other records in the text file form of the database. 4.) After inserting your record (by typing it in) save the file and close it. 5.) Go back into sqlitebrowser and perform the following task: 5.a.) File --> Import --> Database from SQL file 5.b.) In the "open" dialog browse to the location where you saved the text file from step 4. above and open it here. 6.) A dialog will open asking if you wish to create a new database file to hold the imported data. 6.a) Answer "Yes" and save the database in the same location as the current database with a different name. 6.b.) If you answer "No" sqlitebrowser will crash. 6.c.) If you answer "Yes" but attempt to save the database over the current database being used, you will get a dialog stating the following: "File /path/to/your/database/your_database.sqlite already esists. Please choose a different name" with the only option here being an "OK" button. Selecting this button takes you back to the sqlitebrowser where you will have to start over from step 5. above. 7.) Once you have completed step 6.a. above close sqlitebrowser and delete the record of the current database you were attempting to change. 8.) Rename the database saved in step 6.a. to the name of the database that was deleted in step 7. Once step 8 is completed, you have now successfully added a new record to the database via export and import operations. You can open the newly renamed database in sqlitebrowser and if you've followed the above steps correctly you should have a new record located in the database exactly where you placed it in steps 2 through 4 above. This post is currently the only solution for creating a new record until the "new record" button gets fixed as per the original post's bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427401 Title: No new records can be created no matter what settings are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlitebrowser/+bug/1427401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427401] Re: No new records can be created no matter what settings are used.
** Also affects: sqlite Importance: Undecided Status: New ** No longer affects: sqlite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427401 Title: No new records can be created no matter what settings are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlitebrowser/+bug/1427401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427401] [NEW] No new records can be created no matter what settings are used.
Public bug reported: Specifications: OS: Xubuntu 14.04 Desktop: XFCE 4.10 Package: sqlitebrowser v2.0b1 Description of problem: 1.) After using sqlitebrowser to open the camera database contained within a github project called "osm-bundler" (where the database being opened can be found here): https://github.com/HaiyangXu/osm-bundler/blob/master/osmbundler/cameras/cameras.sqlite 2.) The "Browse Data" tab is selected and a view of the types of cameras shown in the database is listed. 3.) A camera must be added to this database so the "New Record" button is selected in order to create a new record. What is expected to happen: A dialogue or window or something should open asking me for the information to be placed in the new record, or a new blank record should be created such that its blank cells could be modified to hold the new data the user wishes to input. What happens instead: A window pops open with an incorrect error message stating the following: Error message begins Error adding record, make sure a table is selected. If the table contain fields declared as NOT NULL please select EDIT->PREFERENCES and adjust the default value for new records to insert an empty string. Error message ends Notes on the above error: Where the above error message occurs even though there is only one table to select and it is selected in the table drop down list located in the upper left area of the programs window, and this error message is also happening regardless of the fact that under the settings "EDIT -> PREFERENCES" the "default value for new records" has been set to be "an empty string". Concise description of the problem: In short, there is no way to stop the error message from happening when attempting to create a new record in the database and as a result no new records can be created. For completeness here is the following requested information: lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 sudo apt-cache policy sqlitebrowser sqlitebrowser: Installed: 2.0.0~beta1+ds.1-3 Candidate: 2.0.0~beta1+ds.1-3 Version table: *** 2.0.0~beta1+ds.1-3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: sqlitebrowser (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/1427401 Title: No new records can be created no matter what settings are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlitebrowser/+bug/1427401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1410609] [NEW] nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build
Public bug reported: What I was doing when the problem occurred: I was alerted to update the system by the system update daemon, and the update was allowed to commence. 1.) Bug report command requested: lsb_release -rd Command results: Description:Ubuntu 14.04.1 LTS Release:14.04 2.) Bug report command requested: sudo apt-cache policy nvidia-331-updates Command results: nvidia-331-updates: Installed: 331.113-0ubuntu0.0.4 Candidate: 331.113-0ubuntu0.0.4 Version table: *** 331.113-0ubuntu0.0.4 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 Packages 100 /var/lib/dpkg/status 331.38-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages 3.) What did I expect to happen: I expected the system to update without problems. 4.) What happened instead: A crash report was automatically generated and sent me to this website where I provided the extra information requested by the bug reporting form. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Tue Jan 13 18:22:06 2015 InstallationDate: Installed on 2014-12-13 (31 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package nvidia trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1410609 Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1410609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220994] Re: [P5E3 Deluxe, AD1988B, playback] No sound at all during "speaker test" under "system settings".
This report needs an appropriate status update and or, if no one else can confirm, then this bug should be closed. I'm not sure which status to choose since I'm not sure what fixed the problem and I don't see any options for closing this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220994 Title: [P5E3 Deluxe,AD1988B, playback] No sound at all during "speaker test" under "system settings". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1220994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220994] Re: [P5E3 Deluxe, AD1988B, playback] No sound at all during "speaker test" under "system settings".
Due to a hard drive crash I have since reinstalled / upgraded to: kernel: 3.8.0-31-generic, OS: Ubuntu 12.04.3 LTS, Desktop: Gnome3, Gnome Shell 3.4.1 ...and this problem doesn't appear to be affecting the system any more. It was probably fixed by an update as suggested in comment #2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220994 Title: [P5E3 Deluxe,AD1988B, playback] No sound at all during "speaker test" under "system settings". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1220994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220994] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all during "speaker test" under "system settings".
Public bug reported: Quick Specs: - OS: Ubuntu 12.04.3, Gnome3 desktop (not classic) Motherboard: ASUS P5E3 DELUXE/WiFi-AP@n alsa-base version: 1.0.25+dfsg-0ubuntu1.1 alsa-tools version: 1.0.25-1ubuntu1 alsa-tools-gui version: 1.0.25-1ubuntu1 alsa-utils version: 1.0.25-1ubuntu5.2 alsamixergui version: 0.9.0rc2-1-9.1 All ALSA version are the ones reported by synaptic package manager. Description of the problem: --- 1.) There is no audio when clicking on the the "test" buttons under the speaker icons located in "System Settings" --> "Audio" --> "Hardware" --> "Speaker Test". Note that I do get audio when doing a similar test from the command line which is partly what makes me think this is a bug. Notes: - 1.) Ubuntu makes it very difficult to figure out which package belongs to which graphical interface. In the "Speaker Test" section of the System Settings mentioned above, I have no way of finding out what package is responsible for that interface. 2.) My speakers are on, and all relevant volume controls have been turned up both in hardware and in software. This is evident by the fact that I can hear audio (although with no way to control the base being at max volume all the time no matter what is done to try and stop this from occurring) from test performed on the command line. 3.) I followed this trouble shooting guide all the way through to the end without solving the problem. https://help.ubuntu.com/community/SoundTroubleshootingProcedure Extra information on the software settings and specs obtained while following this trouble shooting guide can be found here: http://www.alsa-project.org/db/?f=46175bd3a0eecc64a3e60efeec1869080ed89629 4.) I filed a question (with all the information recommended from note 3 above) that no one answered at the following web address: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/235159 5.) I followed the steps outlines at the following web address which brought me here: https://wiki.ubuntu.com/DebuggingSoundProblems Questions: -- If any one knows what package is responsible for the "Speaker Test" graphical interface, can you please explain to me how to bug test this further to see if it is the GUI or if it is some package the GUI is communicating with that is responsible for no sound being heard when clicking on the "test" icons described in the description of the problem above? Specific requested info: === 1.) lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 2.) apt-cashe policy pkgname? Package name still needed, see question above. 3.) What I expected to happen. -- When I clicked on the "test" button under each speaker icon of the 5.1 analog surround sound room map shown under "System Settings" --> "Audio" --> "Hardware" --> "Speaker Test", I expected to hear the relevant audio file played for the speaker icon "test" button that I was clicking on. So for example, if I clicked on the "Front Center" "test" button, I expected to hear the audio "Front Center" to be played over the front center speaker. 4.) What happened instead. No audio was heard at all when clicking on any of the "test" buttons under there respective speaker icons noting that the volume was turned up and that audio could be heard when doing the same test from the command line as follows: speaker-test -Dplug:surround51 -c6 -l1 -twav That command line does produce sound on each speaker with the correct respective audio file (with the exception of the sub-woofer which is labeled LFE in the test but the audio played is "rear center" and appears to come out the front center channel and the sub-woofer at the same time but that problem is most likely a hardware issue). For reference that command also output the following text to the command line while it was performing the speaker tests. speaker-test 1.0.25 Playback device is plug:surround51 Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 22 to 5461 Period size range from 11 to 2730 Using max buffer size 5460 Periods = 4 was set period_size = 1365 was set buffer_size = 5460 0 - Front Left 4 - Center 1 - Front Right 3 - Rear Right 2 - Rear Left 5 - LFE Time per period = 8.564185 Please let me know if I can add any extra information to this request or if I need to clarify my question any further. Thanks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48 Uname: Linux 3.2.0-52-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sysop 20
[Bug 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Oops, sorry I meant to type "12.04, 64bit" and not "12.02, 64bit". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
I can confirm this is happening on my setup as well, but I pretty much have the same setup as the op. 12.02, 64bit and all that so I think my bug report would be pretty much a repeat of what was already posted. Is this problem fixed, or not a problem in the first place on 12.10 or 13.04 releases? Is there a way to get it to install yet or are there any other ways to work arround this problem? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988509] Re: setoption.pl is not executable
This is not fixed in upstream. When doing an upgrade through synaptic, I get the followiing errors every time: First Screens Error Message: E: samba4: subprocess installed post-installation script returned error exit status 1 Next screens error message: ProvisioningError: guess_names: 'realm =' was not specified in supplied /etc/samba/smb.conf. Please remove the smb.conf file and let provision generate it dpkg: error processing samba4 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: samba4 Note: In my case I had to try installing the unstable samba4 package because I can't access any shared network resorces on the desktop from any ones laptop over the local network and this is still the case today. This was working fine in Oneric before the upgrade to Precise. Note: the desktop can access shared folders from other computers that are running older distributions such as 10.04 and 11.04 even with the currently broken samba problems in Precise. Question: 1.) How can I upgrade to the samba4 4.0.0~alpha19+dfsg1-7 fix that was released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988509 Title: setoption.pl is not executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/988509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992820] Re: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126
*** This bug is a duplicate of bug 988509 *** https://bugs.launchpad.net/bugs/988509 Julien DIDRON: I've changed the permissions on setoption.pl as you've described which did get rid of the original error, however the rest of your instruction produced no solution and gave a new error: Here is what happens from the CLI: ~$ sudo dpkg --configure samba4 Setting up samba4 (4.0.0~alpha18.dfsg1-4ubuntu2) ... Administrator password will be set randomly! ProvisioningError: guess_names: 'realm =' was not specified in supplied /etc/samba/smb.conf. Please remove the smb.conf file and let provision generate it dpkg: error processing samba4 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: samba4 ~$ NOTE 01: The only location within the file that contains the text "[netlogon] share" was line 160, and this did not appear to be a declaration of anything. I attempted to add the declaration you gave in that section starting at line 163, and after saving the file and retrying the command given above, the same error message is produced as listed above. NOTE 02: After removing the declaration that was added in NOTE 01 above (since it didn't seem to make a difference), I attempted to follow the error messages suggestions by removing /etc/samba/smb.conf (actually I just renamed it to something unrecognizable by the script that creates it (where the script creating /etc/samba/smb.conf appears to be /usr/share/samba/setoption.pl)), but /usr/share/samba/setoption.pl compained that it couln't write to /etc/samba/smb.conf so I created an empty file and named it smb.conf in the /etc/samba directory. Then /usr/share/samba/setoption.pl wrote two lines to that empty file: Lines written to the file begins realm = server role = dc Lines written to the file ends To clarify since I started with an empty file, the above two lines are the only two lines that were written to, and are the only lines in: /etc/samba/smb.conf at this point. In the original /etc/samba/smb.conf file that was renamed to something unrecognizable by /usr/share/samba/setoption.pl these two lines are already present on lines 292 and 293 respectivly. NOTE 03: Given the informaton from NOTE 01 and NOTE 02 above, it seems that /usr/share/samba/setoption.pl creates an error condition in /etc/samba/smb.conf by creating it with an empty "realm = " string. Quations: 1.) Does anybody know what realm means in this case, and what should it be equal to? 2.) Does any one know how to get /usr/share/samba/setoption.pl to stop creating that empty "realm = " statement in /etc/samba/smb.conf to see if that will fix the problem? If so can you report your results here? Also if any one else is having this problem, please remember to click on the line that is about 7 lines down from the very top of this webpage, titled "This bug affects you and n other person" (where "n" will be some number that represents the numbef of people who have clicked on that line). Clicking on that link helps to rate the importance of this bug report. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992820 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/992820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992820] Re: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126
*** This bug is a duplicate of bug 988509 *** https://bugs.launchpad.net/bugs/988509 Please disregaurd my previous comment. I did not notice that this report was a duplicate of bug #988509. Please refer to the original bug report for more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992820 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/992820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990734] Re: Unable to print to networked printer after fresh install of Ubuntu 12.04 64 bit
*** This bug is a duplicate of bug 973270 *** https://bugs.launchpad.net/bugs/973270 This didn't work for me. For comment #19, when I got to step 1. cupsenable ipp-printer I recieved the following error: cupsenable: Operation failed: client-error-not-found After that point, printing no longer worked locally, and still didn't work remotely. After reinstalling the local printer as a locally connected usb printer, printing locally was restored, and remote printing was still broken. My setup: OS: Kubuntu 12.04 64bit (installed directly to the hard drive, not a virtual install (is that what livebox means?)) DS: KDE v4.8.4 MoBo: Asus P5E3 Delux Mem: 4GB GPU: NVIDIA GeForce 8800 GT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990734 Title: Unable to print to networked printer after fresh install of Ubuntu 12.04 64 bit To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/990734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024210] Re: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024210 Title: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1024210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024210] [NEW] package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
Public bug reported: system crashed during install of kde-full meta-package. a text mode screen opened up aksing if I wated to configure something that looked like remote access to my machine without any explanation of what it was. I decided to kill the process out of paranoia and a crash report was generated on the next login. So here we are. The moral of the story? Don't ask a user if they want to configure remote access. Just assume they don't wan't it in the first place, and don't even attempt to install it unless it was specifically requested by the end user. In my case and to my knowledge I made no such request, and if this was part of the defalut kde-full meta-package, then it should be removed unless you want to see more crash reports like this one. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: lirc 0.9.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 12 22:03:46 2012 ErrorMessage: subprocess installed post-installation script was killed by signal (Killed) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: lirc Title: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) UpgradeStatus: Upgraded to precise on 2012-07-13 (0 days ago) mtime.conffile..etc.lirc.hardware.conf: 2012-07-12T22:12:33.756506 mtime.conffile..etc.lirc.lircd.conf: 2012-07-12T22:12:33.772514 ** Affects: lirc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024210 Title: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1024210/+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
Ok, so apparently attaching files to posts is broken as well. Here are some pastebin links for the debug output files: Output from "sudo gnome-settings-daemon --debug --no-daemon" http://pastebin.com/uJiqU178 Output from "gnome-settings-daemon --debug --no-daemon" http://pastebin.com/yZWVEwmE -- 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
[Bug 649809] Re: the session settings manager can try starting before the login screen one exits
Attached to this post is the non-elevated privilege output: gnome-settings-daemon --debug --no-daemon This debug output basically said: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 193 error_code 2 request_code 154 minor_code 30) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Which I can't really understand. So... My Questions are: 1.) Can the status of this bug for Natty be changed to confirmed or something that more accurately reflects the problems I've shown with these posts? 2.) Is there anything I can uninstall, purge, or swap out with something else to help confirm which packages are effected? 3.) Has this bug become a permanent unsolvable problem in terms of getting themes to work in Natty again? I will attempt a reinstall of various Ubuntu releases to see if I can get this problem to go away. I'm out of idea's other than reinstalling. -- 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
[Bug 649809] Re: the session settings manager can try starting before the login screen one exits
Oops, I forgot that long outputs were not allowed. I'll attatch the debug outputs as log files. Attached to this post is the output of: sudo gnome-settings-daemon --debug --no-daemon Lots of debug info, then it just hangs and does nothing else on the last line. ** Attachment added: "The output from "sudo gnome-settings-daemon --debug --no-daemon"" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/649809/+attachment/3220373/+files/gnome-settings-daemon_debug_with_sudo.log -- 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
[Bug 649809] Re: the session settings manager can try starting before the login screen one exits
None of the proposed solutions so far works for my setup at all. Specs: Distribution: Ubuntu 11.04 64Bit (Actual machine, NOT a virtual machine) Codename: Natty Narwhal Desktop: Gnome 2 CPU: Intel Quad Core 2 Extreme, X9650, 64Bit, (3GHz per core) GPU: GeForce 8800 GT GPU MEM: 512 MB GPU MEM Interface: 256 MB GPU VBIOS: 62.92.24.00.00 MoBo: Asus MoBo MEM: 4GB Right clicking on the desktop and selecting "Change Desktop Background" results in the following error message: Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with DBus, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager. Any attempt at starting the gnome-settings-daemon such as: sudo gnome-settings-daemon results in the following error messages: ** (gnome-settings-daemon:6805): WARNING **: Failed to acquire org.gnome.SettingsDaemon ** (gnome-settings-daemon:6805): WARNING **: Could not acquire name Here is the output from "apt-cache policy gnome-settings-daemon" gnome-settings-daemon: Installed: 2.32.1-0ubuntu13.1 Candidate: 2.32.1-0ubuntu13.1 Version table: *** 2.32.1-0ubuntu13.1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status Any attempt at killing and restarting the gnome-settings-daemon produces no significant change. I will list one debug output with elevated privileges, and one without. Here is the debug output after killing and restarting the gnome-settings-manager with elevated privileges: ~$ sudo gnome-settings-daemon --debug --no-daemon ** (gnome-settings-daemon:20326): DEBUG: Successfully connected to D-Bus ** (gnome-settings-daemon:20326): DEBUG: Starting settings manager ** (gnome-settings-daemon:20326): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/ ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Mouse' file='/usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin' location='mouse' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Clipboard' file='/usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin' location='clipboard' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Accessibility Keyboard' file='/usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin' location='a11y-keyboard' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='X Resource Database' file='/usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin' location='xrdb' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='XRandR' file='/usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin' location='xrandr' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Font' file='/usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin' location='font' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='X Settings' file='/usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin' location='xsettings' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Typing Break' file='/usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin' location='typing-break' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Media keys' file='/usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin' location='media-keys' ** (gnome-settings-daemon:20326): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin ** (gnome-settings-daemon:20326): DEBUG: GnomeSettingsPluginInfo: name='Keyboard' file='/usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin' location='keyboard' ** (g
[Bug 1023622] Re: Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running"
** Tags added: gnome-settings-daemon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1023622 Title: Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1023622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1023622] [NEW] Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running"
Public bug reported: My system: Distribution: Ubuntu 11.04 64Bit Codename: Natty Narwhal Desktop: Gnome 2 CPU: Intel Quad Core 2 Extreme, X9650, 64Bit, (3GHz per core) GPU: GeForce 8800 GT GPU MEM: 512 MB GPU MEM Interface: 256 MB GPU VBIOS: 62.92.24.00.00 MoBo: Asus (Can't remember which one, too lazy to look it up, probably not important for this report) MoBo MEM: 4GB Description of the problem: My themes got screwed up, possibly form the installation of one of any of the following packages. All the Ubuntustudio packages I could find in synaptic were installed except for the Ubuntustudio desktop (I prefer Gnome 2). "Desktop Geometry Switcher" a.k.a. grandr 0.4.1 was added to the Gnome panel by right clicking on the Gnome panel and selecting "Add to panel" Compiz Fusion, with "Grid" enabled under Window Management Settings Latest release of LibreOffice 3.5 (a version not found in the package manager but a *.deb downloaded and installed from the maintainers website) Steps that first caused the problem after the above installations were completed: Left clicked on the "Desktop Geometry Switcher" icon and selected "left". What was expected: That grandr would behave as it normally does and would ask me if the current display settings were correct, and that the display would be rotated 90 degrees in the counter-clockwise direction and that all would be well and fine with my currently chosen (customised) theme and icons. What happened instead: The display was immediately rotated 90 degrees in the counter-clockwise direction without any messages asking me if it was ok, and my chosen theme and icon set has been switched to some (painful to look at) default theme and icon set with no way to switch it back to what I had. Attempting to do anything theme related such as right clicking on the desktop and selecting "Change Desktop Background" results in the following error message: Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with DBus, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager. Any attempt at starting the gnome-settings-daemon such as: sudo gnome-settings-daemon results in the following error messages: ** (gnome-settings-daemon:6805): WARNING **: Failed to acquire org.gnome.SettingsDaemon ** (gnome-settings-daemon:6805): WARNING **: Could not acquire name Here is the output from "apt-cache policy gnome-settings-daemon" gnome-settings-daemon: Installed: 2.32.1-0ubuntu13.1 Candidate: 2.32.1-0ubuntu13.1 Version table: *** 2.32.1-0ubuntu13.1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status Questions: 1.) Is there any way to get my themes and icons working again? 2.) Is there any way to fix this problem? ** Affects: gnome-settings-daemon (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/1023622 Title: Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1023622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
As of 2012 Wed, July 11, This bug is still happening in Ubuntu 11.04 Natty 64Bit My themes are broken, and nothing appears to work in order to get the gnome-settings-daemon working properly again. If I attempt to fix the incorrect desktop theme by right clicking on the desktop and selecting "Change Desktop Background" I get the following error message: Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with DBus, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager. Here is the command issued from the CLI: sudo gnome-settings-daemon Here is its output: ** (gnome-settings-daemon:6805): WARNING **: Failed to acquire org.gnome.SettingsDaemon ** (gnome-settings-daemon:6805): WARNING **: Could not acquire name I've tried many suggested workarounds but nothing is fixing this problem. Do Mint or Archlinux suffer from this problem? I need a distro that works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/384439 Title: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/384439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1018115] Re: package libelektratools2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libelektratools.so.2.0.0', which is also in package elektra 0.7.0-1~getdeb1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1018115 Title: package libelektratools2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libelektratools.so.2.0.0', which is also in package elektra 0.7.0-1~getdeb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elektra/+bug/1018115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1018115] [NEW] package libelektratools2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libelektratools.so.2.0.0', which is also in package elektra 0.7.0-1~getdeb1
Public bug reported: error occurred during installation via synaptic package manager airport suggested an error report and brought me to this page. No further information is available at this time. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: libelektratools2 (not installed) ProcVersionSignature: Ubuntu 2.6.38-15.60-generic 2.6.38.8 Uname: Linux 2.6.38-15-generic x86_64 NonfreeKernelModules: nvidia AptOrdering: libelektra3: Install libelektratools2: Install libelektra3: Configure elektra-bin: Configure libelektratools2: Configure Architecture: amd64 Date: Tue Jun 26 13:44:11 2012 ErrorMessage: trying to overwrite '/usr/lib/libelektratools.so.2.0.0', which is also in package elektra 0.7.0-1~getdeb1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcVersionSignature_: Ubuntu 2.6.38-15.60-generic 2.6.38.8 SourcePackage: elektra Title: package libelektratools2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libelektratools.so.2.0.0', which is also in package elektra 0.7.0-1~getdeb1 UpgradeStatus: Upgraded to natty on 2011-10-22 (248 days ago) ** Affects: elektra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1018115 Title: package libelektratools2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libelektratools.so.2.0.0', which is also in package elektra 0.7.0-1~getdeb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elektra/+bug/1018115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373767] Re: Incorrect keyboard mapping
Update: Mathias Weyland's ppa isn't responding. I've tried several servers both in the US and through proxies in other countries and can not get a connection to Weyland's ppa at the moment. If this ppa is no longer active can someone else please step in and help shed some light on how Weyland might have figured out how to fix the keymap from scratch. I've read through the documentation, but either the documentation doesn't say anything about what a hardware keycode looks like in tiemu format, or if tiemu even needs a special format for a keycode, or how to find a keycode, or any examples of how to map a "hardware keycode" in tiemu's keymap file, or any alternate methods of mapping keys for tiemu besides the ones mentioned in the keymap file etc. or I just havent found where it says any of that stuff, in any of the documentation yet. If you know any of the answers please feel free to share them. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373767 Title: Incorrect keyboard mapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiemu/+bug/373767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183039] Re: tiemu window shrinks until smallest window size is achieved
I can also verify that this bug is persistent for: tiemu v3.02 with a Ti89 titanium ROM under Ubuntu 11.04 Note: I'm booting into the gnome desktop instead of the default unity desktop, and I'm also using Compiz window manager which allows me to use CTRL+ALT+[numpad 4 or numpad 6] to make any window orient to the left or right hand side of the screen, and as long as I don't try to resize tiemu in any way (either through any of its preferences or by click- dragging its window) then the CTRL+ALT+[numpad option] seems to allow tiemu to remain full size to one side of the screen. However it doesn't sit next to the edge of the screen like it should, and if I try to move it it might try to edge snap to fill the screen in which case the bug takes over and it shrinks to its smallest size and CTRL+ALT+numpad6 doesn't work again until I close the program and reopen it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183039 Title: tiemu window shrinks until smallest window size is achieved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiemu/+bug/183039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373767] Re: Incorrect keyboard mapping
The above post is fairly old by now, and as a result I was wondering if any one had any updates as to the progress of this unfortunate problem with tiemu on Ubuntu. For my own issues with tiemu I need to know the correct key mappings for TiEMU v3.02, using a Ti89 titanium ROM, inside Ubuntu 11.04. Generally: Could you please provide some more detail on how you were able to fix the key mappings? Specifically: It would help if you could provide an example of some important lines in your keymap file so that I might get some idea of how to solve the problem on my end. Also, any examples of 1.) How you found the hardware key codes for your keybord. 2.) How you found what those key codes were being interpreted as inside TiEMU 3.) ...and how you got TiEMU to recognize the key codes correctly. ...would be a huge help and might go a long way to helping others figure out how to create a solution for there own particular OS / distro / TiEmu version etc. P.S. If your still around, is your ppa still active, would it solve my issues as described earlier in this post? Thanks. Hope someone is still around to answer this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373767 Title: Incorrect keyboard mapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiemu/+bug/373767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692736] Re: pstocanonij missing on amd64
dorpm Please be more specific. I am having the same problem you were having, but because you were not verbose in your post, I am unable to resolve the issue. Can you please explain how you were able to get your printing problems resolved in more detail so the rest of us might benefit from your experience? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692736 Title: pstocanonij missing on amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/692736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43379] Re: nm-applet vanished, disappears from tray
I can also confirm that this bug still seems to be present in v11.04 Natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/43379 Title: nm-applet vanished, disappears from tray To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/43379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 729150] Re: libappindication crashes in gtkstatusicon code on update
I apologies for my last comment. I just woke up and didn't quite have my brains with me yet. It should be noted however that having status indications at the top of the page that say "fix released" might be a little confusing to new people, or experienced people who are in a sleep induced confused panic just after they wake up like I was. Again my apologies, if there is a moderator perhaps this message and the one before it can be removed from the thread so as to keep it on topic. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729150 Title: libappindication crashes in gtkstatusicon code on update To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/729150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 729150] Re: libappindication crashes in gtkstatusicon code on update
I clicked on "fix released" and it took me to this comment page without any link to a fix. How do I find where the fix link is for Natty? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729150 Title: libappindication crashes in gtkstatusicon code on update To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/729150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 751114] Re: ffmpeg unresolvable dependancies
I've solved the problem I was having in post #23 above. I had to install libavutil49 first before the upgrade would work. Here is the truncated output: ~$ sudo apt-get install libavutil49 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libavcodec52 libavformat52 The following packages will be REMOVED: libavcodec-extra-52 libavutil-extra-49 The following NEW packages will be installed: libavcodec52 libavutil49 The following packages will be upgraded: libavformat52 1 upgraded, 2 newly installed, 2 to remove and 5 not upgraded. Need to get 2,643kB of archives. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? Y Fetched 2,643kB in 2s (1,218kB/s) Setting up libavutil49 (4:0.5.1-1ubuntu1.1) ... Setting up libavcodec52 (4:0.5.1-1ubuntu1.1) ... Setting up libavformat52 (4:0.5.1-1ubuntu1.1) ... Processing triggers for libc-bin ... ~$ sudo apt-get update Fetched 3,758B in 3s (970B/s) Reading package lists... Done ~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: ffmpeg libavdevice52 libavfilter0 libpostproc51 libswscale0 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 647kB of archives. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? Y Fetched 647kB in 1s (348kB/s) Setting up libavdevice52 (4:0.5.1-1ubuntu1.1) ... Setting up libavfilter0 (4:0.5.1-1ubuntu1.1) ... Setting up libpostproc51 (4:0.5.1-1ubuntu1.1) ... Setting up libswscale0 (4:0.5.1-1ubuntu1.1) ... Setting up ffmpeg (4:0.5.1-1ubuntu1.1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place synaptic shows all packages up to date and security fixes in place. Thanks for all the helpful suggestions. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/751114 Title: ffmpeg unresolvable dependancies -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 751114] Re: ffmpeg unresolvable dependancies
I followed Jeff's Steps (https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/751114/comments/18) and this did NOT fix it. Here is my output: ~$ sudo apt-get update Fetched 3,758B in 3s (976B/s) Reading package lists... Done ~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: ffmpeg libavdevice52 libavfilter0 libavformat52 libpostproc51 libswscale0 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. Does any one else have any other thoughts or possible fixes for this, or is my only option to do multiple distribution upgrades like Nach0 explains in post #14 of this bug thread?: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/751114/comments/14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/751114 Title: ffmpeg unresolvable dependancies -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693906] [NEW] The language used in the OpenSSH Server documentation page is misleading or incorrect.
Public bug reported: Binary package hint: ubuntu-docs 1st: The reason why this report is being filed here is due to the following statement: At the bottom of the OpenSSH Server Page it states the following: "To report a problem, visit the bug page for Ubuntu Documentation" Where "bug page for Ubuntu Documentation" is a link to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs If this is not the place to file this report, then the link listed above needs to be changed on that page. The page for which this report is in reference too: https://help.ubuntu.com/9.10/serverguide/C/openssh-server.html The section of the page for which this report is in reference too: The section entitled "SSH Keys". Problem: This page is in reference to installing and configuring OpenSSH server, but in the section at the bottom of the page entitled "SSH Keys" it states the following: "ssh-copy-id usern...@remotehost" The word "remotehost" should be changed to "remoteclient" unless "host" was really the intended word in which case a larger problem is revealed. Assuming that the host is the server that is hosting a client, then this page is in reference to setting up the host, and there should be no dialogue in reference to the host being "remote" because we are physically sitting at the machine where the host is being set up in the first place. Request: Could someone please fix the wording on the given page or move the "SSH Keys" section to the client side setup documentation of OpenSSH? Also, could the OpenSSH documentation be more clearly separated into client and host sections in general? This would greatly improve the readability of the documentation and would make it much easier to follow. Thanks. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Tags: documentation openssh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693906 Title: The language used in the OpenSSH Server documentation page is misleading or incorrect. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 165113] Re: gksudo nautilus won't set ownership/permissions on files below
My Setup: Ubuntu 10.04 64bit, kernel v2.6.32-25-generic, standard release gnome desktop. This bug is present on my computer. I mainly encounter it because I share my computer with my wife. She has her account and I have mine. I am the system administrator of my computer, and when the need arises to transfer a file or make a shared director for doing such. Often times the files that appear in that share folder or transfered file end up with root permissions only. As such I have to change the ownerships and groups back to something that can be viewed and shared by both I and my wife. It doesn't bother me to use the command line or to write an executable script that is linked to an icon, I just wish I didn't have to do this for every new release of Ubuntu to get around this issue in Nautilus. Did the permissions function work in nautilus on earlier versions of Ubuntu? Did it ever work? If so, what broke it originally? Whats keeping it broken now? Just curious. -- gksudo nautilus won't set ownership/permissions on files below https://bugs.launchpad.net/bugs/165113 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 606929] Re: When switching to another user account, after about 12 hours I get logged out when I try to switch back to my account.
I've discovered a work around for this bug. First some extra notes that I forgot to mention about replicating this bug: 1. Both accounts should lock after an amount of time specified by the default screen saver settings in Ubuntu. 2. You should be logged into the other users account for a long period of time (this bug occurs after I've left the computer on over night so at least 6 to 8 hours, and not the 12 that I mentioned in the first message). The work around: Log into the currently active non-administrative user account before switching out of it back to the administrative account. Result: For whatever reason this seems to keep the administrative account from logging out when you select the login button. Again, if there is any extra information that I can give to help track down this bug further please let me know. -- When switching to another user account, after about 12 hours I get logged out when I try to switch back to my account. https://bugs.launchpad.net/bugs/606929 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 606929] Re: When switching to another user account, after about 12 hours I get logged out when I try to switch back to my account.
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52122039/Dependencies.txt ** Attachment added: "LoginDefs.txt" http://launchpadlibrarian.net/52122040/LoginDefs.txt -- When switching to another user account, after about 12 hours I get logged out when I try to switch back to my account. https://bugs.launchpad.net/bugs/606929 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 606929] [NEW] When switching to another user account, after about 12 hours I get logged out when I try to switch back to my account.
Public bug reported: I absolutely do know the package this bug is in reference too but for whatever reason this launchpad bug report webpage would not let me submit the package name stating the following error: "login (1:4.1.4.2-1ubuntu2)" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" Note: When I gave it the package name "login by itself" the website directed me to select one of a number of phrases, non of which had anything to do with this package. Here is a link to the package that has the bug this report is in reference too: http://packages.ubuntu.com/lucid/admin/login The package name listed when executing "apt-cache policy login" from the CLI: login: Installed: 1:4.1.4.2-1ubuntu2 Candidate: 1:4.1.4.2-1ubuntu2 Version table: *** 1:4.1.4.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Note: Please fix the launchpad website bug report page to include or at the very least recognize the package named: "login (1:4.1.4.2-1ubuntu2)" or "login" Here is the bug report: System info: OS: Ubuntu Lucid Lynx 10.4 (64bit version) Kernel: Linux 2.6.32-23-generic Desktop: GNOME 2.30.2 Motherboard: ASUS p5edelux CPU: Intel Quad Core 2 Extreme (X9650) Mem: 4GB To recreate this problem: 1. Login to an account with administrative privileges. 2. Stay logged on that account but switch to another account that doesn't have administrative privileges. 3. Remain in the non-administrative account for about 12 hours or over night. 4. Try and switch back to the administrative account that you logged into in step 1 above. What I expected to happen: I should have been switched back into my administrative account. What happened instead: Some text was briefly shown on a black screen (too fast to see what it was) and I was logged out of my account. This shouldn't be happening. If I want to stay logged in it should let me stay logged in. Especially if i have some important jobs running in the background. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: login 1:4.1.4.2-1ubuntu2 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 Architecture: amd64 Date: Sun Jul 18 08:25:09 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: shadow ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug login lucid -- When switching to another user account, after about 12 hours I get logged out when I try to switch back to my account. https://bugs.launchpad.net/bugs/606929 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
