Confirmed for Intrepid 8.10, installed from alternate CD yesterday with
current updates.
Removing plasma-appletsrc solves the problem, but yields an additional
K-Menu in the control bar at the next login, where the Alt+F1 seems to
work at the right one.
Removing the left one of the K-Menus from
Great new problem solution strategy discovered: Known bug becomes
invalid by sheer waiting (a lump one and a half year only) for expiry
of support! Magnificent!
--
no sound after feisty upgrade
https://bugs.launchpad.net/bugs/110799
You received this bug notification because you are a member of
Confirming this bug for Gutsy release.
[rant]Shouldn't bug reports from beta testers at the very least be
assigned before release?[/rant]
--
[Gutsy] Thunderbird doesn't open http link in firefox
https://bugs.launchpad.net/bugs/136303
You received this bug notification because you are a member
I think it indeed is the same problem an in 90950: The samba share
cannot be accessed from a windows machine either. (Checked from a
virtual machine.)
But I'm unsure if it is really samba that were to be blamed: The
smb.comf manpage
(http://de.samba.org/samba/docs/man/manpages-3/smb.conf.5.html)
This bug definitely is not related to samba configuration by some GUI,
only: I did not use any samba GUI, just upgraded from Edgy to Feisty and
got that msdfs proxy = no line in my smb.conf!
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug
I cannot confirm not having had this line before the upgrade (because I
have no backup from the Edgy files). The information that the line only
came with Feisty was a hint from a previous discussion after I noted
(from the file date) that something obviously had touched the smb.conf
during the
Thanks Brian for wondering and for taking the time to ask. Do you have
any questions concerning this bug?
This indeed is no longer an issue for me: As you may have expected,
I've looked for possible workarounds in the meantime. In fact, I've
moved the related files to another system, now having
Kalinda, did you look for a line msdfs proxy = no in your smb.conf,
removed it and did a sudo /etc/init.d/samba restart and your problem
remained? Then this might be a different issue.
Concerning downgrading, mrvanes said on 2007-03-24: Downgrading samba,
samba-common, smbclient and libsmbclient
Public bug reported:
I'm running three systems on Feisty (one upgraded from Edgy, two set up
from scratch). On all of these, sound output fails with KMPlayer.
There seems to be neither a basic hardware problem, nor a problem with
the related sound driver: MP3-files are flawlessly played in
** Description changed:
I'm running three systems on Feisty (one upgraded from Edgy, two set up
from scratch). On all of these, sound output fails with KMPlayer.
There seems to be neither a basic hardware problem, nor a problem with
the related sound driver: MP3-files are flawlessly
found this to be known bug 91500 in xine, solution known at least since
2007-03-12.
solved mine as described in https://bugs.launchpad.net/ubuntu/+source
/xine-lib/+bug/91500
--
no sound after feisty upgrade
https://bugs.launchpad.net/bugs/110799
You received this bug notification because you
Chris, Ubuntu has come with a claim that was new to me (I'm no primer to
Linux, too) when looking on Linux, where I was used to it as Windoze
user for long: Simplicity to use. Period. Not only for some freaks but
for the typical user who just desperately believes he will really get
what he sees.
Public bug reported:
Binary package hint: mozilla-thunderbird
.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue May 1 09:06:59 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/mozilla-thunderbird/mozilla-thunderbird-bin
Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7494122/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7494123/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7494124/Disassembly.txt
** Attachment
Got that crash report after system restart, where I don't remember if in
this case it was a clean shutdown (thru the KDE system's K-menu) or a
forced power-down because the system hung (with blinking cursor on black
screen) while hibernating. In case this happens again, I will come back
to this
Error still persists in today's upgrade to samba_3.0.24-2ubuntu1.2.
(Temporaryly inserted the msdfs proxy line for testing purpose.)
Would be interesting to know if anybody from the samba team only
recognized this bug: Still not assigned to nobody, importance still
undedided, status on needs info
You're right, KDE should be blamed for misconfiguring samba.
But samba should kindfully ignore OBVIOUS misconfiguration!
(Or would no ever be judged a valid network path to a CIFS share?)
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug
Chris, I admit that I would stop insisting, too, were I kinda sure this
erraneous behaviour would not be generated again because KDE was fixed.
But as far as I have followed the discussion, the initial action in fact
was a change in samba, making it more sensitive to an obvious
misconfiguration
Alexander, so this bug by definition is none because it only relates
to kde? If it came to gnome, you surely would have fixed it before
release? But with kde, there even was no need to comment for about one
year?
John, thanks for your courtesy of at least changing importance from
won't fix to
Hey, that's really a great strategy to company success! - After a bug
report, just wait some years until the system is out of support:
Most probably the user that reported the bug will no longer be
interested in filing a new report. (Maybe he has indeed changed system
because it was unusable, but
@Tormod Volden:
current status: System as mentioned in #7 and following, startx from
recovery mode, system locked with black screen, hard reset
console
r...@beta:~# file /var/log/Xorg.0.log
/var/log/Xorg.0.log: empty
/console
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
@Przemysław: No, I obviously cannot verify if this bug still exists.
As you may (or rather may not) have read from the above, this was an
automated crash report, for which I was unable to tell the actual reason
two years ago. After some of those crashes, I switched back to KMail,
which I still
@Przemysław: Sorry, you are probably the wrong addressee for my above
rant. I don't worry about the community dropping work on my bug report
after End Of Life of the related product.
What disappoints me (and what renders reporting crashes meaningless) is
the fact that a bug after being confirmed
Public bug reported:
Binary package hint: openoffice.org-writer
In OpenOffice.org 3.1.1 (from the Ubuntu repositories), the letter wizard fails
to start: After calling the wizard from the menu (German version
Datei-Assistenten-Brief..., translates to something like
File-Wizards-Letter...)
** Attachment added: OOo error message on wizard start w/o JRE
http://launchpadlibrarian.net/37677059/20100110_JRE_aktivieren.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37677060/Dependencies.txt
--
wizard req'ing JRE fail to start (solution hint)
confirming behaviour described 2009-07-13 with Karmic
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Don't now if it's the same bug, but an at least very similar behaviour
struck me with an FSC Amilo M 6300, 166 MHz Celeron, 1 GB RAM, 86C380
ProSavageDDR K4M266 after clean install of Jaunty (Kubuntu or Xubuntu
from alternate CD): hard lock on X startup, xorg.conf is empty, lshal
yells
error:
** Attachment added: lshal output on hardy
http://launchpadlibrarian.net/28978470/lshal
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: lspci -vvnn on Jaunty (recovery mode)
http://launchpadlibrarian.net/28979495/lspci-vvnn
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Xorg.0.log on Jaunty (recovery mode) after failed start
with kdm
http://launchpadlibrarian.net/28979792/Xorg.0.log
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you
** Attachment added: lspci -vvnn on Hardy (kdm graphic mode)
http://launchpadlibrarian.net/28980100/lspci-vvnn
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Xorg.0.log on Hardy (kdm graphic mode)
http://launchpadlibrarian.net/28980120/Xorg.0.log
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks Jonathan for wondering and taking the time to ask - even about
two years after the original posting.
As reported about one and a half years ago, I have been working with a
workaround since. I am sorry but I won*t be able to rebuild the systems,
involved in the erraneous situation described
Public bug reported:
affected system is my (somewhat outdated) FujitsuSiemens notebook model
Amilo M Series, I used for installation (1) kubuntu Dapper LiveCD 6.06
LTS and (2) kubuntu Edgy alternateCD 6.10 (no internet available for
installation).
By (1) I installed Dapper, immediately
** Description changed:
affected system is my (somewhat outdated) FujitsuSiemens notebook model
- Amilo M Series, I used for installation (1) kubuntu Dapper LiveCD 6.06
- LTS and (2) kubuntu Edgy alternateCD 6.10 (no internet available for
- installation).
+ Amilo M Series (kubuntu hardware
Public bug reported:
systems involved are
(1) alpha: SuSE 9.2 based, /etc/export (extract) reads /intradisk
beta(rw,root_squash) gamma(rw,root_squash)
(2) beta: Kubuntu 6.10 Edgy (installed from scratch by LiveCD, current
updates, kubuntu hardware database cd6f858209b5b21dd911e0bd9f34078e)
and
Nope. In the meantime I've rebuilt the system from scratch using a
LiveCD. Sorry.
--
Update to Edgy by alternateCD knocks down the system
https://launchpad.net/bugs/70729
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Description changed:
Binary package hint: flashplugin-installer
- in upgrading from kubuntu 8.04 to 9.10 using adept, my network was
+ in upgrading from kubuntu 8.04 to 9.04 using adept, my network was
temporarily unavailable during package update for flashplugin-installer.
after
Public bug reported:
Binary package hint: flashplugin-installer
in upgrading from kubuntu 8.04 to 9.10 using adept, my network was
temporarily unavailable during package update for flashplugin-installer.
after reestablishing the network, the update process remained at something like
150 .
Jonathan:
Tried adding vcards as vcard (not converting to akonadi) - and failed:
No addressbook is added (respective window in kaddressbook remains
empty).
--
kaddressbook fails to show addressbooks contents
https://bugs.launchpad.net/bugs/676173
You received this bug notification because you
Public bug reported:
Binary package hint: kdepim
kadressbook, first started after LogOn, shows two seeming empty addressbooks:
- Personal Contacts (/home/user/.local/share/contacts/) and
- akonadi_vcard_resource_1 (/home/user/.kde/share/apps/kabc/std.vcf)
After closing/restarting
Update: Canonical support suggests
$ sudo apt-get install --reinstall kdepim
This Inst's and Conf's additional packages kalarm, kjots, knode and
konsolekalendar, but fails to solve the problem.
--
kaddressbook fails to show addressbooks contents
https://bugs.launchpad.net/bugs/676173
You
Update: Canonical support suggests
$ sudo apt-get install --reinstall kaddressbook
This Inst's and Conf's kaddressbook, but again fails to solve the
problem
--
kaddressbook fails to show addressbooks contents
https://bugs.launchpad.net/bugs/676173
You received this bug notification because
Update: Canonical support suggests fresh install of 10.04 or upgrade to
10.10. Both for me currently is a no-op.
Further information about the system as from the support case: On my machines
(with different hardware, but common NFS /home on a separate NAS device)
Kubuntu 10.04 was installed
Jonathan:
The problem I need solved is the following:
In KDE-Resources, there are three addressbooks installed and active:
- /home/user/.kde/share/apps/kabc/std.vcf (vcard),
- /home/user2/.kde/share/apps/kabc/std.vcf (vcard, read only) and
- akonadi-resource
Some weeks ago, I remember having
corrupt bootsplash image appears to be known plymouth bug #571567
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
appears to be solved for Lucid for the system mentioned 2009-07-13 -
great work, thanx to the team!
btw, would someone from the team mind telling us out in the wild what
the problem was about?
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
some additional information:
fresh install from the Kubuntu 10.04 desktop CD did it, only the
bootsplash image appears to be displayed with 8 colors (similar to
attachment).
starting (not installing) Kubuntu from the same CD got me a hanging
system again.
** Attachment added: Kubuntu plymouth
Indeed, the NFS server appears to be about 2 minutes in the future - I
will try to fix this. - Meanwhile...
$ akonadictl stop
$ rm -r ~/.local/share/akonadi/
$ rm -r ~/.config/akonadi/
$ akonadictl start
Connecting to deprecated signal
Adding as KDE Address Book (traditional) appears to work. However, the
resulting addressbook seems magically to be filled automatically with
further addresses from whatever source - which is neither what I
expected nor wished to happen.
--
You received this bug notification because you are a
Sorry for my panicking answer - it seems that only the last of about
1300 adresses from the vcf file were read very slowly. Yes, I can add
entries, they are saved on closing Kontact - and after restarting, I can
also delete them.
Is this vcf file now duplicate defined in Kontact? - Even before
KMail in KDE PIM 4.4 is not Akonadi enabled and I think it will
read addresses through the old KDE Resources mechanism
while KAddressBook will read them through Akonadi.
From what actually happened to my system, I would have concluded to
exactly the contrary:
I had the old vcf addressbook
Wiping the Akonadi database fixed the problem
Nope, sorry: Wiping the Akonadi database had no visible effect at all as
to the problem discussed. - The solution was (in addition to the
definition in the KDE Resources) to use the old KDE Resources
mechanism in KAddressBook.
Another possibly
We found the error in the Akonadi logs and fixed it by recreating the
database.
Sorry for insisting: The symptom of the error initially described was
addressbooks def'ed in the KDE Resources not showing up in KAddressBook,
but however the addresses being accessible in KMail.
I got you right in
the KDE Resources mechanism is no longer used in KAddressBook.
Interesting. So witchcraft gives user2 access to the addressbooks in
KAddressBook? They are (as previously for user) *only* def'ed by the KDE
Resources mechanism.
--
You received this bug notification because you are a member of
If you have further issues or queries
Thanks for the kind hint. In the moment, I have no further issues or
queries apart from those raised - and remaining unanswered - in this bug
(and the original support case, of course).
If I had just one wish to fulfill by canonical support (that I've paid
$ akonaditray
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
$ systray
Der Befehl »systray« wurde nicht gefunden, meinten Sie vielleicht:
Befehl »systraq« aus dem Paket »systraq« (universe)
systray: Befehl nicht gefunden
The latter
As mentioned in #9, $ akonaditray just yields an error message, but no
icon visibly appears (neither in the systray, nor elsewhere).
Before fuddling around with PPA-versions (that from my experience tend
to produce more then to solve problems), I would prefer to know what the
error is basically
$ akonadictl status
Akonadi Control: running
Akonadi Server: running
Akonadi Server Search Support: not available
$ akonadictl stop
$ sleep 30
$ akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
Akonadi Server Search Support: not available
$ akonadictl start
Connecting
copied the above commands to test.sh:
$ sh test.sh
insgesamt 0
srwxrwxrwx 1 user mygroup 0 2010-12-10 18:23 mysql.socket
insgesamt 24
-rw-r--r-- 1 user mygroup 2736 2010-12-10 18:25 akonadiserver.error
-rw-r--r-- 1 user mygroup 1114 2010-12-10 18:23 akonadiserver.error.old
srwxr-xr-x 1 user
60 matches
Mail list logo
