Re: [Bug 85311] Re: gnome-power-manager misbehaves and goes into endless loop
I am sorry, but I am unable to reproduce it even with my current laptop, which is running Edgy Eft. The phenomenon I had reported was visible in my earlier laptop. I have a feeling that this was being caused by an unusual interaction between the ACPI layer in the firmware and the GNOME power manager. I do not know how to reproduce it now. Shuvam On 8/9/07, Pedro Villavicencio <[EMAIL PROTECTED]> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. The issue that you reported is one that should be > reproducable with the live environment of the Desktop CD of the > development release - Gutsy Gibbon. It would help us greatly if you > could test with it so we can work on getting it fixed in the next > release of Ubuntu. You can find out more about the development release > at [WWW] http://www.ubuntu.com/testing/ . Thanks again and we appreciate > your help. > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Incomplete > > -- > gnome-power-manager misbehaves and goes into endless loop > https://bugs.launchpad.net/bugs/85311 > You received this bug notification because you are a direct subscriber > of the bug. > -- gnome-power-manager misbehaves and goes into endless loop https://bugs.launchpad.net/bugs/85311 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 45500] Re: When trying to set up a printer in http://localhost:631/ an error occurs
This is 2008 March and I've just upgraded from Edgy to Gutsy (v7.10). And this problem is hitting me. It was not there in Edgy earlier. The description _exactly_ matches what others have described above, therefore I am not adding any new description. I've done a dist-upgrade about five minutes ago, and before that I've also uninstalled cupsys and a host of other packages and reinstalled them. -- When trying to set up a printer in http://localhost:631/ an error occurs https://bugs.launchpad.net/bugs/45500 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 67111] Re: Cyrus linked against db4.4 compiled against 4.3 ?
Am a little new to Debian and Ubuntu, hence don't know how this bugfix process works. Am I reading you right if I conclude that you are releasing the new, bugfixed version of Cyrus 2.2 only on Fiesty, and the Edgy release will not contain the bug-fix? If I'm right, I'll have to download the Cyrus source from the Edgy source archives and apply this Debdiff and recompile? Please can you confirm/deny? Shuvam On 2/23/07, Steve Kowalik <[EMAIL PROTECTED]> wrote: > Attached is a debdiff for uploading to edgy-proposed. This bug is a > regression from Dapper, and is actually quite nasty. The init script > fires off a master process which spawns off an imapd and/or pop3d > process. They die horribly with a SEGV due to this libdb brain damage, > are immediately re-spawned by the master process, and proceed to die > again. Rinse and repeat. > > The debdiff fixes the bug by patching configure (which the Debian build > does anyway) to not include db4.4 in it's list of libdb versions. > > ** Attachment added: "debdiff" >http://librarian.launchpad.net/6516492/cyrus-edgy-proposed.debdiff > > -- > Cyrus linked against db4.4 compiled against 4.3 ? > https://launchpad.net/bugs/67111 > -- [SRU]: Cyrus linked against db4.4 compiled against 4.3 ? https://launchpad.net/bugs/67111 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 67111] Re: [SRU]: Cyrus linked against db4.4 compiled against 4.3 ?
> @Shuvam: currently the fix for edgy is on its way. It will however need > to go to the edgy-proposed repository first so that it can get a wider > testing before it can finally go to edgy-updates. > > You can find the exact details of the process at > https://wiki.ubuntu.com/MOTU/SRU. Thanks. Will look. :) Shuvam -- [SRU]: Cyrus linked against db4.4 compiled against 4.3 ? https://launchpad.net/bugs/67111 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 67111] Re: [SRU]: Cyrus linked against db4.4 compiled against 4.3 ?
> If you didn't use Daniel's packages, you should still be using libdb 4.3 > databases, and so just need to upgrade to the packages in edgy-proposed > and see if they work. I didn't use Daniel's test packages. Do I just add a line replacing 'edgy' with 'edgy-proposed' in /etc/apt/sources.list and apt-get install this package? Which packages exactly need to be installed? I am asking because there are many packages which make up Cyrus 2.2. Sorry about the confusion, but I'm new to this bug-tracking and updating thing. Shuvam -- [SRU]: Cyrus linked against db4.4 compiled against 4.3 ? https://launchpad.net/bugs/67111 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85311] gnome-power-manager misbehaves and goes into endless loop
Public bug reported: Binary package hint: gnome-power-manager I am running Ubuntu Edgy Eft on a Lenovo Thinkpad R40e laptop. The gnome-power-manager occasionally goes into an endless loop, constantly reducing and increasing screen brightness ad nauseum. When this happens, it increases CPU load considerably. This happens almost every time when the laptop wakes up from hibernation, and also occasionally after a few hours of the laptop's operation. This sudden malfunction is not related to a switch in the power supply state, i.e. is not related to any switch from AC to battery power or vice versa. My simple and effective workaround is to do the following: $ killall gnome-power-manager $ gnome-power-manager This has worked every time so far. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-power-manager misbehaves and goes into endless loop https://launchpad.net/bugs/85311 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85316] Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20
Public bug reported: Binary package hint: cyrus-common-2.2 Cyrus 2.2: the cyrmaster goes into an endless loop logging the following messages through syslog: Feb 14 18:32:36 lap2 cyrus/notify[19204]: Fatal error: wrong db version Feb 14 18:32:43 lap2 cyrus/master[4463]: process 19204 exited, signaled to death by 11 Feb 14 18:32:43 lap2 cyrus/notify[19209]: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20 This goes on forever. The only way to stop this is to bring down cyrus by running "/etc/init.d/cyrus2.2 stop" ** Affects: cyrus-imapd-2.2 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20 https://launchpad.net/bugs/85316 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85316] Re: Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20
I am running Ubuntu Edgy Eft, and have done a dist-upgrade in the last two days, so this linking error is current as of 12 Feb Edgy Eft. -- Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20 https://launchpad.net/bugs/85316 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 85316] Re: Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20
*** This bug is a duplicate of bug 67111 *** > *** This bug is a duplicate of bug 67111 *** > > ** This bug has been marked a duplicate of bug 67111 >Cyrus linked against db4.4 compiled against 4.3 ? > > -- > Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked > against 4.4.20 > https://launchpad.net/bugs/85316 Okay, thanks. :) Shuvam -- Cyrus 2.2: incorrect version of Berkeley db: compiled against 4.3.29, linked against 4.4.20 https://launchpad.net/bugs/85316 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519768] [NEW] After hard reboot, hal doesn't restart on reboot, ever
Public bug reported: Binary package hint: hal After hard reboot, the system reboots and comes to the text-mode screen on tty1. It never reaches the GUI. And this is not a temporary problem -- it persists through all subsequent reboots of the system. If I log in at the text-mode prompt, become root, and then do the following: service hal start service gdm start then the GUI screen comes back up, and the system is healthy. If I reboot the system again, any number of times, I always face the same need to start hal manually, followed by gdm. The only non-standard things I can think of, in my Ubuntu installation, are (i) my /var/log is on a separate file system, not on the root file system, and (ii) my home dir too is on that separate file system, not on root. Other than these, I do not know of anything else which is non-standard in my case, and I do not know whether these are relevant for this problem or not. This is repeatable. It has happened to myself and a colleague, both using Thinkpad X-series laptops and the exact same Ubuntu version, installed from the same copy of live CD. Both of us have the same separate file system for homedir, logs, etc, with softlinks from the root-fs. Both of us had laptop hangs on different occasions, and had to do a hard reboot. We got this problem after that, and then in my laptop's case, it went away only after I re-formatted the HDD and re-installed Ubuntu again from the CD. ProblemType: Bug Architecture: i386 Date: Wed Feb 10 15:38:18 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: vmnet vmci vmmon Package: hal 0.5.13-1ubuntu8 ProcEnviron: PATH=(custom, user) LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: hal Uname: Linux 2.6.31-14-generic i686 ** Affects: hal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- After hard reboot, hal doesn't restart on reboot, ever https://bugs.launchpad.net/bugs/519768 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 519768] Re: After hard reboot, hal doesn't restart on reboot, ever
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39002035/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/39002036/XsessionErrors.txt -- After hard reboot, hal doesn't restart on reboot, ever https://bugs.launchpad.net/bugs/519768 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 519768] Re: After hard reboot, hal doesn't restart on reboot, ever
The only cure I know for this problem is to re-install Ubuntu from scratch again. Till that time, however, the system remains healthy as long as I don't reboot the OS --- this means I can use my laptop for weeks, as long as I just suspend it and wake it up. Hibernate and wakeup also works correctly. -- After hard reboot, hal doesn't restart on reboot, ever https://bugs.launchpad.net/bugs/519768 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 519775] [NEW] Irritating continuous log messages from modem-manager
Public bug reported: Binary package hint: modemmanager Lines keep appear in syslog logfiles, for service "daemon", of this type: Feb 10 16:48:57 lap4 modem-manager: (Huawei): (ttyUSB1) deferring support check Feb 10 16:49:00 lap4 modem-manager: (ttyUSB1): re-checking support... Feb 10 16:49:00 lap4 modem-manager: (Huawei): (ttyUSB1) deferring support check Feb 10 16:49:03 lap4 modem-manager: (ttyUSB1): re-checking support... Feb 10 16:49:03 lap4 modem-manager: (Huawei): (ttyUSB1) deferring support check Feb 10 16:49:06 lap4 modem-manager: (ttyUSB1): re-checking support... Feb 10 16:49:06 lap4 modem-manager: (Huawei): (ttyUSB1) deferring support check These go on and on forever. Sometimes, after a suspend-wakeup, these lines stop. At other times, these lines continue forever. Removing the Huawei PCMCIA CDMA data card (I presume that's what this is about) and re-inserting it back does not seem to stop these messages. The card works correctly. Therefore, it is not affecting my work, other than creating big logfiles which are harder to search through. ProblemType: Bug Architecture: i386 Date: Wed Feb 10 16:49:52 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: vmnet vmci vmmon Package: modemmanager 0.2.git.20091014t233208.16f3e00-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: modemmanager Uname: Linux 2.6.31-14-generic i686 ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Irritating continuous log messages from modem-manager https://bugs.launchpad.net/bugs/519775 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 519775] Re: Irritating continuous log messages from modem-manager
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39002196/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/39002197/XsessionErrors.txt -- Irritating continuous log messages from modem-manager https://bugs.launchpad.net/bugs/519775 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 518411] [NEW] apparmor prevents cups-pdf from printing to ~/PDF
Public bug reported:
Binary package hint: apparmor
My cups-pdf cannot print to my ~/PDF if apparmor is active. Doing "service
apparmor stop"
allows printing-to-PDF to happen.
I suspect this is because my /home/username is a symlink to
/warehouse/home/username.
(My laptop's /warehouse is a separate partition). Whether this is caused
because I have
a symlink in the path, or because there is a file-system-boundary traversal by
the
symlink, I don't know.
I found that adding two lines to /etc/apparmor.d/usr.sbin.cupsd solved
the problem:
/warehouse/home/shuvam/PDF/ rw,
/warehouse/home/shuvam/PDF/* rw,
@{HOME}/PDF/ rw,
@{HOME}/PDF/* rw,
The two @{HOME} lines were already present --- I just added the
/warehouse/home/...
lines. It is therefore clear that something additional needs to be done about
apparmor
configuration for cups-pdf if there is a symlink or a file-system-traversal in
the path
of the ~/PDF.
I don't know whether this is an apparmor bug or a cups-pdf bug.
ProblemType: Bug
ApparmorStatusOutput:
Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not
have enough privilege to read the profile set.
apparmor module is loaded.
Architecture: i386
Date: Sun Feb 7 20:23:17 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: vmnet vmci vmmon
Package: apparmor 2.3.1+1403-0ubuntu27.3
ProcEnviron:
PATH=(custom, user)
LANG=en_IN
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: apparmor
Uname: Linux 2.6.31-14-generic i686
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
apparmor prevents cups-pdf from printing to ~/PDF
https://bugs.launchpad.net/bugs/518411
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 518411] Re: apparmor prevents cups-pdf from printing to ~/PDF
** Attachment added: "ApparmorPackages.txt" http://launchpadlibrarian.net/38859661/ApparmorPackages.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38859662/Dependencies.txt ** Attachment added: "KernLog.txt" http://launchpadlibrarian.net/38859663/KernLog.txt ** Attachment added: "PstreeP.txt" http://launchpadlibrarian.net/38859664/PstreeP.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38859665/XsessionErrors.txt -- apparmor prevents cups-pdf from printing to ~/PDF https://bugs.launchpad.net/bugs/518411 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 1384206] Re: vuze crashes on startup
The output which I get from vuze when I fire it from my command-line. ** Attachment added: "Stdout+stderr when running "vuze" from command-line" https://bugs.launchpad.net/ubuntu/+source/azureus/+bug/1384206/+attachment/4241751/+files/vuze-out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384206 Title: vuze crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azureus/+bug/1384206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384206] [NEW] vuze crashes on startup
Public bug reported: Vuze crashes on startup, every time. I start it from the command-line by typing "vuze". It fails to start when launched from the menu too. IMPORTANT: when I install Ubuntu 14.04 on my laptop and then install Vuze, it starts up and operates correctly. I then install other packages. At some point, after I have installed many other packages, Vuze fails to start up. I have verified this twice by re-formatting my hard drive and re-installing Ubuntu 14.04 each time from scratch. This behaviour is repeatable. Since there seems to be some problem here caused by the other packages I have installed, I will attach the list of packages I have installed on my laptop. Version of Ubuntu (lsb_release -rd): Description:Ubuntu 14.04.1 LTS Release:14.04 Version of Vuze I am using (from the output of dpkg-query -l): 4.3.0.6-5 WHAT I EXPECT: that Vuze will start up and show a large window with its usual controls WHAT ACTUALLY HAPPENS: Vuze reports an error from the Java VM and exits promptly, without any delay or processing, and gives me the shell prompt again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vuze 4.3.0.6-5 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 22 17:14:41 2014 PackageArchitecture: all SourcePackage: azureus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: azureus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "List of packages installed on my laptop currently" https://bugs.launchpad.net/bugs/1384206/+attachment/4241748/+files/dpkg-query-output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384206 Title: vuze crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azureus/+bug/1384206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384206] Re: vuze crashes on startup
Since the problem is a Java exception, I suspect the debugger will want to know what Java libraries and files I have on my laptop. Therefore I have included the "ls -l" of my /usr/share/java ** Attachment added: "Directory listing of /usr/share/java" https://bugs.launchpad.net/ubuntu/+source/azureus/+bug/1384206/+attachment/4241752/+files/javadirlist.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384206 Title: vuze crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azureus/+bug/1384206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 519768] Re: After hard reboot, hal doesn't restart on reboot, ever
Actually, even on Karmic, this problem disappears if I reinstall Karmic. I believe I had explained that phenomenon. And on other, later releases of Ubuntu, the problem does not seem to occur. In any case, even on Karmic, the problem began occurring after a hard reset. I have not used other releases long enough to have to do a hard reset, therefore my observations are inconclusive there. Shuvam On Wed, Jun 01, 2011 at 12:00:39PM -, madbiologist wrote: > Support for Karmic has ended. Later versions of Ubuntu have replaced > HAL with Udev. Is this still occurring on Ubuntu 11.04 "Natty Narwhal"? > > ** Changed in: hal (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/519768 > > Title: > After hard reboot, hal doesn't restart on reboot, ever > > Status in “hal” package in Ubuntu: > Incomplete > > Bug description: > Binary package hint: hal > > After hard reboot, the system reboots and comes to the > text-mode screen on tty1. It never reaches the GUI. And > this is not a temporary problem -- it persists through all > subsequent reboots of the system. > > If I log in at the text-mode prompt, become root, and then > do the following: > > service hal start > service gdm start > > then the GUI screen comes back up, and the system is > healthy. If I reboot the system again, any number of times, > I always face the same need to start hal manually, followed > by gdm. > > The only non-standard things I can think of, in my Ubuntu > installation, are (i) my /var/log is on a separate file system, > not on the root file system, and (ii) my home dir too is on > that separate file system, not on root. > > Other than these, I do not know of anything else which is > non-standard in my case, and I do not know whether these > are relevant for this problem or not. > > This is repeatable. It has happened to myself and a > colleague, both using Thinkpad X-series laptops and the > exact same Ubuntu version, installed from the same copy > of live CD. Both of us have the same separate file system > for homedir, logs, etc, with softlinks from the root-fs. > Both of us had laptop hangs on different occasions, and > had to do a hard reboot. We got this problem after that, > and then in my laptop's case, it went away only after I > re-formatted the HDD and re-installed Ubuntu again from > the CD. > > ProblemType: Bug > Architecture: i386 > Date: Wed Feb 10 15:38:18 2010 > DistroRelease: Ubuntu 9.10 > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) > NonfreeKernelModules: vmnet vmci vmmon > Package: hal 0.5.13-1ubuntu8 > ProcEnviron: >PATH=(custom, user) >LANG=en_IN >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-14.48-generic > SourcePackage: hal > Uname: Linux 2.6.31-14-generic i686 > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/hal/+bug/519768/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/519768 Title: After hard reboot, hal doesn't restart on reboot, ever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/519768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892665] [NEW] gnome-shell occupy much space in my pc
Public bug reported: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892665 Title: gnome-shell occupy much space in my pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1892665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742851] [NEW] Whenever I try to install nvidia system never opens after reboot
Public bug reported: Whenever I try to install nvidia system never opens after reboot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50~14.04.1 [modified: boot/vmlinuz-4.4.0-31-generic] ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Jan 12 08:52:51 2018 InstallationDate: Installed on 2018-01-11 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742851 Title: Whenever I try to install nvidia system never opens after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1742851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704536] [NEW] after installing java 8 system said there a problem occured while installing java 8
Public bug reported: shuvam@shuvam-Inspiron-3558:~$ java -version java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) shuvam@shuvam-Inspiron-3558:~$ javac -version javac 1.8.0_131 it is still showing this ProblemType: Package DistroRelease: Ubuntu 16.04 Package: java-common 0.56ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jul 15 14:04:38 2017 Dependencies: ErrorMessage: package java-common is already installed and configured InstallationDate: Installed on 2017-07-15 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: dpkg Title: package java-common 0.56ubuntu2 failed to install/upgrade: package java-common is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704536 Title: after installing java 8 system said there a problem occured while installing java 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1704536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
