I have the same problem as the OP, although timed alarms are always
displayed those with 'all day event' selected do not.
Platform
Xubuntu 14.04 beta -- 64bit
Orage version -- 4.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Correction to the above.
If you start it with "synaptic &" then it freezes. If you start it with
"synaptic" , leaving the terminal open, then it doesn't freeze.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I have the same problem with Synaptic on Mint15 Cinnamon. It occurs
however I start Synaptic, even through the terminal, and the exact time
of the freeze is completely random, sometimes a few minutes, sometimes
after just one click.
--
You received this bug notification because you are a member o
Satish the only thing I might add to this is that in my experience, when
you do the 'shorting' of the cl1 cl2 pins the machine must have power
available, it is no good doing it with the battery removed it wont work,
in fact the machine has to be switched on. (see my post dated
"2012/11/21 18:38" on
Update to comment 15. Ubuntu12.10, kernel 3.5.0-23 64bit.
After 2 days of use (mount count now 14) the 'recovery' error message
recurred (see comment #13). The file system was "recovered" on every
boot until I forced an fsck from another distro. As before, the fsck
reported no file system errors,
Since forcing fsck from another distro, the warning on file system
recovery on my Ubuntu partition (given in post 13), has not returned.
Prior to forcing this check it occurred on every boot. This makes me
wonder if the decision to set maximum mount count for all ext4 files
systems to -1 was actual
For my next experiment I rebooted from Ubuntu12.10 into Mint14 and forced an
fsck on the Ubuntu partition.
Fsck found no errors.
However when I rebooted into Ubuntu the 'recovery' error was not present this
time.
There continue to be no 'orphan' errors.
--
You received this bug notification bec
These are my initial results. Using the 3.5.0-23 kernel 64 bit on Ubuntu 12.10.
Installed the kernel and did 5 reboots. No instance of orphaned inodes occurred:
grep -i orphan /var/log/syslog
ubuntu@fujitsu
The 'recovery' message occurred on every boot, but then again it also
occurs on every boot
I can confirm that I am using AHCI mode also. I will start testing the
3.5.0-23 kernel today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105900
Title:
Latest Kernel Version 3.2.0-36 Causing EXT4
I have an identical problem on Ubuntu 12.10 when using kernel 3.5.0-22
but not kernel 3.5.0-21
Jan 22 18:44:21 fujitsu kernel: [2.865532] EXT4-fs (sda2): orphan cleanup
on readonly fs
Jan 22 18:44:21 fujitsu kernel: [2.866295] EXT4-fs (sda2):
ext4_orphan_cleanup: deleting unreferenced in
In my case all the distros I am using are 64bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093617
Title:
Kernel 3.5.0-21 will not shutdown on uefi booted machines
To manage notifications about
** Also affects: linux-lts-quantal (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/1093617
Title:
Kernel 3.5.0-21 will not shutdown on uefi booted
Ah, thank you again YannUbuntu.
That is not the answer then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks out UEFI firmware (~bios) access
To manage notif
I am not at all familiar with Uefi workings, so the following comment is
neither a solution nor even a theory, simply a question for others that
are familiar with Uefi to consider.
I see that in my /boot/efi folder I have the following files:
ls -l /boot/efi/EFI/Microsoft/Boot/
total 480
-rwxr-xr
That is a shame morlock, it seemed like a much easier solution all
round.
Well done for finding it even if it doesn't work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI
morlock, thank you very much for this work.
I have tried all three of your nvram dumps on my machine and none of
them make any difference to its behaviour. In other words f2 settings
menu and f12 boot choices continue to be available at all times even
when in running your 'nvram_fucked_up' state.
I can confirm that the advice given by morlock has returned my bios to
working order, though I don't think this marks the bug as solved as it
is just a workround and will probably recur if Ubuntu is reinstalled.
The bios contains no settings related to Uefi that I can find (ie I
can't switch it of
@YannUbuntu
I confirm I used the Erase Disk option to install Ubuntu.
@Chris Murphy
Your reference to Uefi settings confuses me. In my terminology, a bios is a
hard coded chip attached to a motherboard which has settings accessed by
pressing f2 at boot up for such things as setting the boot order
Public bug reported:
lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
apt-cache policy grub-efi-amd64
grub-efi-amd64:
Installed: 2.00-7ubuntu11
Candidate: 2.00-7ubuntu11
Pheonix Secure Core Tiano bios version 1.09
New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled.
I am using kernel 2.6.31.17 now and I have also tested lucid kernel
2.6.32.4 as well. Neither of these kernels solve the Huawei E220 'loop'
bug. I have a 2.6.32 kernel on Sidux and that does work with the E220,
but only if you use usb-modeswitch as well (version 1.0.7 in my case).
Usb-modeswitch ma
+1 for the above comment - it has not been fixed in the 31.16 kernel.
--
Huawei E220 and E169 3G dongle do not work on karmic (major regression)
https://bugs.launchpad.net/bugs/430011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Very sorry but I don't use Ubuntu any more and I have sold the computer
that had the problem so I can no longer help you.
--
Evesham Voyager laptop will not shut down
https://bugs.launchpad.net/bugs/173435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
phontanka:
I have also tried every version of Suse linux from 10.0 to 10.3 and I have had
nothing but trouble with all of them. Graphics problems, sound problems,
internet problems, mouse problems, keyboard problems, in fact too many problems
to make it worth my while bothering with. I actually
Leann,
I have been testing Hardy since the first day it was released right up
till the present. Sad to say it is no nearer to shutting down my laptop
now than it ever has been.
What may be of interest to you though is that about a couple of months
ago I started using another distribution and this
This problem has been cured by using the latest proprietary ati driver
installer (version 8.452) followed by aticonfig.
--
Blank screen with lates restricted-modules update
https://bugs.launchpad.net/bugs/186124
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This error has been cured by a subsequent update.
Unfortunately I can't tell you which one.
** Changed in: ubuntu
Status: New => Fix Released
--
Hardy recovery mode fails
https://bugs.launchpad.net/bugs/172872
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Binary package hint: linux-restricted-modules
Ever since the linux-restricted-modules was upgraded from version 2.6.24.5-4.12
I have been unable to boot kubuntu Hardy. I have tried version 2.6.24.6-4.15
and 2.6.24.6-5.16 on both kernel 2.6.24.4 and 2.6.24.5 and on all occas
Out of interest I tried the downgrade of libhsqldb-java to the Gutsy
version, but it made no difference on my system, no element of open
office will run. I have a theory that this may be architecture specific
in some way. I have asked this question on the forums and from the
replies I got those wit
Further still to the above. Downgrading the hal version to the original
has now restored both optical and usb mounting, so perhaps all it needed
to make it work was a reinstallation of hal.
--
no CD automount after upgrade to gutsy (Hal, dbus or gvm)
https://bugs.launchpad.net/bugs/161044
You rec
Further to the above, although my mounting of optical media is now
working correctly, I am now unable to mount usb media except manually,
so perhaps this is not such a good idea after all.
--
no CD automount after upgrade to gutsy (Hal, dbus or gvm)
https://bugs.launchpad.net/bugs/161044
You rece
I have come up with a workround for this problem which is successful for
me. I replaced the default hal 0.5.9-1ubuntu6 which is in the gutsy
repos with hal 0.5.10-5ubuntu1 from the hardy repos. Optical media
recognition now behaves as it should.
One word of warning if you are tempted to try this.
I've got it now as well (on Gutsy) only just noticed as I have been
using Hardy most of the time since the Alpha came out and that does not
have the bug. Neither does Linux Mint (based on Gutsy) on the same
machine.
--
no CD automount after upgrade to gutsy (Hal, dbus or gvm)
https://bugs.launchp
This error has been cured after recent updates.
Thank you all.
Merry Christmas to those who celebrate it.
** Summary changed:
- Errors after Hardy update
+ Errors after Hardy update(solved)
--
Errors after Hardy update(solved)
https://bugs.launchpad.net/bugs/175597
You received this bug notif
2007-12-11 16:53:28 startup packages remove
2007-12-11 16:53:28 status installed digikam 2:0.9.2-2ubuntu2
2007-12-11 16:53:35 remove digikam 2:0.9.2-2ubuntu2 2:0.9.2-2ubuntu2
2007-12-11 16:53:35 status half-configured digikam 2:0.9.2-2ubuntu2
2007-12-11 16:53:35 status half-installed digikam 2:0.9.
Public bug reported:
After recent update to Hardy Heron several applets in kde taskbar no longer
function.
Trash applet permanently empty
System Menu applet empty
Storage Media applet empty
All of these applets present an error message on startup saying: 'malformed url
system:/, malformed url m
Thank you very much for this solution Vladimir, I have been wrestling
with this problem for ages and until now have not found a way to fix it.
Funny thing is that unchecking 'Mount as User' is the exact opposite of
what you would expect to do!!
Thanks again.
I will now go and test it on Hardy and
I can confirm that the behaviour is identical in Hardy. With the 'Mount
as User' option checked the drive is unmountable. Uncheck it and full
read/write access becomes possible.
--
[gutsy] ntfs usb hdd not mounted in kubuntu
https://bugs.launchpad.net/bugs/158309
You received this bug notificatio
You will find an answer to this in bug #158309.
--
User cannot mount automatically ntfs external drive
https://bugs.launchpad.net/bugs/147655
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@
Further Information:
Contrary to my earlier report the point at which the recovery mode fails
is not always during USB installation. For example, the last two times I
have tried booting Hardy recovery mode the boot has stalled at the line
reading:
'sd 2:0:0:0 Attached scsi generic sg2 type 0'
Al
My fresh install of Hardy has exactly the same problem as described
here, kcontrol is empty and all the modules that should be in there are
under 'Lost and Found' in the KDE menu.
--
KControl and KInfoCenter are empty after Gutsy upgrade
https://bugs.launchpad.net/bugs/152325
You received this bu
Thank you very much for offering to help with my shutdown problem. I
will attach the information you requested shortly. BTW the site that you
referred me to asks for the output of lspci -wnn, -w is not a valid
option for lspci so I presume you need the output of -vnn which is what
I have attached.
** Attachment added: "detais.txt"
http://launchpadlibrarian.net/10699033/detais.txt
--
laptop will not shut down
https://bugs.launchpad.net/bugs/173435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
kern.log.0 after suspend
NB it did not resume but had to be shut down with the power button and
then restarted.
** Attachment added: "kern.log.0"
http://launchpadlibrarian.net/10699107/kern.log.0
--
laptop will not shut down
https://bugs.launchpad.net/bugs/173435
You received this bug notifi
kern.log.0 after Hibernate
NB It never completed hibernation - had to be shut down with the power
button and restarted, although strangely enough it did resume from the
hibernated disk image.
NB I have included this information re Hibernate and Suspend as you have
asked for it but for my own pers
PS Neither hibernate nor suspend work properly either, they don't
recover.
--
laptop will not shut down
https://bugs.launchpad.net/bugs/173435
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
** Attachment added: "detais.txt"
http://launchpadlibrarian.net/10691757/detais.txt
--
laptop will not shut down
https://bugs.launchpad.net/bugs/173435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
Public bug reported:
Evesham Voyager C530RD laptop. Kubuntu Hardy Heron Alpha 1.
I would like to renew this bug report in view of my recent change to
Heron Alpha 1, although it has been present in every version and every
distro I have ever tried since owning the machine just over a year ago.
Lap
I have recently completed a fresh install of Kubuntu Hardy Alpha 1 64
bit on my 64bit laptop. I am still unable to boot into recovery mode
(although normal mode is fine). This time the boot does not stop at USB
configuration but stops with the following error:
ALERT! /dev/disk/by-uuid//dev/sda6 do
Fresh install of Kubuntu Hardy Alpha 1 on amd 64 architecture.
I can confirm this problem, all instances of kdesudo return the 'Command not
found' Error. This is particularly difficult in kde-systemsettings where it is
impossible to access the Administrator mode.
The program is installed at 'usr
** Attachment added: "system details"
http://launchpadlibrarian.net/10643446/details
--
Hardy recovery mode fails
https://bugs.launchpad.net/bugs/172872
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Public bug reported:
Multiple attempts to boot Hardy into recovery mode have all failed,
furthermore they have all failed at the same point which is configuring
USB devices. The normal mode of Hardy does not have this problem, it
only occurs in recovery mode. The symptoms are a freeze of the recov
*** This bug is a duplicate of bug 87023 ***
https://bugs.launchpad.net/bugs/87023
I think it might be something to do with the timing of the password
cache. This time I waited 30 minutes and after that time it asked me for
a password again so it is working I guess.
/var/run/sudo/username doe
*** This bug is a duplicate of bug 87023 ***
https://bugs.launchpad.net/bugs/87023
Well, I have just waited over 20 minutes and my password is still
remembered, I can launch any root program without re-entering it.
--
User account 'remembers' admin password
https://bugs.launchpad.net/bugs/13
*** This bug is a duplicate of bug 87023 ***
https://bugs.launchpad.net/bugs/87023
Ah now this is interesting, this is the first time I have ever heard
about any time limit on password caching. I have reinstalled kdesudo and
straight away the 'remember' function has returned, so I will wait 15
I can confirm this error with virtualbox. I have both the virtualbox-ose
and virtualbox-source-ose packages installed and I still get the same
error. The installation instructions in /usr/share/doc make no
difference to this situation, I have carried them out but I still get
the VM-DRIVER-NOT-INSTA
*** This bug is a duplicate of bug 87023 ***
https://bugs.launchpad.net/bugs/87023
Thank you for your time in looking into this, if having your passwords
remembered indefinitely is a wanted purpose on your system then it
certainly isn't on mine so we will have to disagree there. I have
deleted
As of today my shutdown options have returned. It must have been one of
the latest updates that did it although I have no idea which one. Anyway
it is working again - thanks!
--
shutdown options missing
https://bugs.launchpad.net/bugs/136987
You received this bug notification because you are a me
Now added kdebase 4.3.5.7-1ubuntu19 but still no shutdown options.
(also tried kernel 2.6.22-11 to no avail)
--
shutdown options missing
https://bugs.launchpad.net/bugs/136987
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase in ubunt
Upgrade to kdebase 4.3.5.7-1ubuntu18 has not cured this problem.
--
shutdown options missing
https://bugs.launchpad.net/bugs/136987
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROT
Thanks for reply that is now done, bug #136987.
--
If GDM is the default display manager KDE logout dialog is missing shutdown and
restart options
https://bugs.launchpad.net/bugs/64695
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase
Public bug reported:
Binary package hint: kdebase
KUbuntu Gutsy, 64 bit laptop.
Since the update to kdebase 4.3.5.7-1ubuntu17 on Saturday September 1st.
I have had no options in kde logout menu other than 'log out' ie
shutdown and reboot are missing. I was told that a fix had been released
but I
A similar problem to this has occurred on my kubuntu gutsy 64bit
installation following upgrade to kdebase 4.3.5.7-1ubuntu17.
The only shutdown option I have is 'logout'.
Of course it differs slightly in that being a kubuntu system it is not
using gdm display manager but kdm.
--
If GDM is the d
OK I see what you mean.
Like I said, I have removed kdesudu and my functionality has returned to normal
and so far I haven't noticed anything untoward from not having the package
installed.
--
User account 'remembers' admin password
https://bugs.launchpad.net/bugs/132456
You received this bu
This was solved by a later update.
Thanks people - great work!
** Summary changed:
- Unable to install hplip update on Kub64
+ SOLVED Unable to install hplip update on Kub64
--
SOLVED Unable to install hplip update on Kub64
https://bugs.launchpad.net/bugs/132640
You received this bug notificat
*** This bug is a duplicate of bug 87023 ***
https://bugs.launchpad.net/bugs/87023
** Visibility changed to: Public
--
User account 'remembers' admin password
https://bugs.launchpad.net/bugs/132456
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
Public bug reported:
Binary package hint: hplip
Update 'hplip2.7.7-0ubuntu3' will not install on Kubuntu 64bit version.
The following errors are generated:
hplip:
Depends: hplip-data (>2.7.7) but 1.7.3-0ubuntu4 is to be installed
Depends: hplip-firmware (>=2.7.7) but it is not installable
*
I run gutsy on an Evesham Voyager laptop and it still doesn't power off.
I've also tried every boot cheat code you have ever heard of plus a few
you haven't, I still have to hold down the power button every time. That
is the 2.6.22-9 kernel and still no joy.
--
Power down after shutdown does not
*** This bug is a duplicate of bug 102782 ***
https://bugs.launchpad.net/bugs/102782
This now appears to be working normally again.
Solved for me anyway.
--
Adept-updater announces new version of Kubuntu but does not allow it to be
installed
https://bugs.launchpad.net/bugs/103607
You receiv
*** This bug is a duplicate of bug 102782 ***
https://bugs.launchpad.net/bugs/102782
Having the same issue with kubuntu Gutsy on amd64 arch. starting today
(August 8th).
$ adept_updater -v
Qt: 3.3.7
KDE: 3.5.7
Adept Updater: 2.1 Cruiser
$ uname -r
2.6.22-9-generic
--
Adept-updater announce
*** This bug is a duplicate of bug 130470 ***
https://bugs.launchpad.net/bugs/130470
Scott, You guessed right I am on AMD64 architecture and that obviously
was the problem, the latest set of updates cured everything.
Thank you for your time and thank you for this excellent distro,
although Gu
Scott: Thank you very much for the prompt reply and interesting to note that
not everyone is experiencing this problem. I will try to be more specific.
When I say 'break' I mean that any of the above mentioned updates insist on
removing 'kubuntu-desktop' which as far as I understand is an integr
Using Gutsy Gibbon tribe 3.
--
updates break kubuntu
https://bugs.launchpad.net/bugs/130503
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/
Public bug reported:
Binary package hint: kubuntu-desktop
All of the following recently released updates break kubuntu by trying
to remove 'kubuntu-desktop'.
apt
apt-utils
aptitude
debtags
libept0
python-apt
synaptic
** Affects: kubuntu-meta (Ubuntu)
Importance: Undecided
Status:
73 matches
Mail list logo
