I have tried the smbclient and samba packages and everything seems to be
working great thanks.
I seem to get odd messages saying the connection does not exist but you click
on it a second time and off it goes.
I will try and be more precise if needed.
I now need to find out how I can make a
I now need to find out how I can make a samba file system connection
as seamless as connecting to directory on the computer.
I mentioned smbnetfs above.
http://smbnetfs.sourceforge.net/
sudo apt-get install smbnetfs
man smbnetfs
Enjoy!
--
gvfsd-smb crashed with SIGSEGV in strlen()
My Dell mini9 also had the same problem. Procedure in comment 23 also
fixed mine.
--
I cannot connect to any server. Conection hangs up at channel 0: open confirm
rwindow 0 rmax 32768
https://bugs.launchpad.net/bugs/237894
You received this bug notification because you are a member of Ubuntu
I understand that it might not be recommended to do cross major version
upgrades, but it is one of the (usually) strong points of the APT
system, and indeed, I've rarely had any issues doing such things in the
past. However, normally there's a ncurses dialog that mentions a few
things, possibly
In order to silence the bayes database sync messages that are frequently
sent via cron, could you consider fix along the lines of
--- /usr/sbin/amavisd-new-cronjob 2008-10-11 07:17:30.0 +0300
+++ /tmp/amavisd-new-cronjob2009-01-12 09:20:53.960773192 +0200
@@ -29,7 +29,7 @@
Public bug reported:
Binary package hint: rhythmbox
This used to work in intrepid, but in jaunty, rhythmbox throws
everything in the device's root instead of in the Music directory. This
has two bad effects:
* Internally, the device uses FAT, with a ~100 file limit in the root
* The music
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Actually this seems to be a bug in the musepack plugin, but figuring out
why it's crashed is going to pretty much be impossible without the file.
Any chance you can recover it or locate it again? If so, please provide
it here.
** Changed in: audacious-plugins (Ubuntu)
Sourcepackagename:
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Visibility changed to: Public
** Changed in: audacious-plugins (Ubuntu)
Sourcepackagename:
Closing as expired, since there's not enough info to debug this.
Also, it appears this is crashing in some 'crossfade' plugin, but I'm
seeing no sign of that in the audacious source code, nor in audacious-
plugins. So maybe this bug is misfiled anyway.
** Changed in: audacious (Ubuntu)
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
OK I have KDE 4.1.3 version, i saw it i help acerca de.. more eassier way than
instead of what oyu said, I dont know how to do it..I dont find thw folder I
search kdebase-bin and kdebase-plasma packages.
Since I post this more updates Adept has done but none to fix that crash, so I
read on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Public bug reported:
Binary package hint: kino
When exporting to MPEG/DVD, the estimated remaining time seems wildly
pessimistic, eg: 20 hours for a project which will complete in about an
hour. Perhaps the initial time taken to lock audio is not being
subtracted from the time taken so far,
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Hi Michael,
I reproduced the crash, but gdb indicated nothing.
As you can see above I get an 'please run dpkg --configure -a' error. I
did this and include the output bellow and in file.
One more question though:
Is there any relevance to this bug? I ran it from the live cd and not
many people
** Attachment added: gdb-dpkg--configure-a.log
http://launchpadlibrarian.net/21098398/gdb-dpkg--configure-a.log
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: gdb-gdb.txt
http://launchpadlibrarian.net/21098400/gdb-gdb.txt
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: gdb-gdb.log
http://launchpadlibrarian.net/21098405/gdb-gdb.log
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: gdb-update-manager.txt
http://launchpadlibrarian.net/21098407/gdb-update-manager.txt
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: gdb-update-manager.log
http://launchpadlibrarian.net/21098409/gdb-update-manager.log
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: update-manager-c-d-1.png
http://launchpadlibrarian.net/21098425/update-manager-c-d-1.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: update-manager-c-d-2.png
http://launchpadlibrarian.net/21098426/update-manager-c-d-2.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: update-manager-c-d-3.png
http://launchpadlibrarian.net/21098432/update-manager-c-d-3.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: update-manager-c-d.png
http://launchpadlibrarian.net/21098435/update-manager-c-d.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: apport-gtk.png
http://launchpadlibrarian.net/21098440/apport-gtk.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Confirmed as (apparently) fixed (or worked around) in 8.10 with
2.6.27-11-generic. This probably doesn't apply to 8.04 LTS though - ie
Long Term Support, hint hint.
--
[gutsy tribe 5] Fails to handle systems with too many IDE interfaces
https://bugs.launchpad.net/bugs/137619
You received this
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Changed in: gnome-applets
Status: Unknown = New
--
intrepid: system tray volume applet does not hide automatically anymore
https://bugs.launchpad.net/bugs/279462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Description changed:
Binary package hint: network-manager
Hi,
I'm running ubuntu intrepid ibex (8.10) on a Dell Vostro 1310 laptop.
- Networkmanager is unable to setup my wired connection via dhcp. It has
- no problem with profiles with fixed ip address. Let me explain the
-
The problem is now fixed thanks.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
iwl3945 wifi card not working
https://bugs.launchpad.net/bugs/278552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
The problem has been fixed with the 1.3.9-2ubuntu6 update. Thanks.
--
cups: 127.0.0.1:631 - Address already in use.
https://bugs.launchpad.net/bugs/304393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
I was really surprised there was no supported way to clear the location bar.
Furthermore, this problem persists in 3.0.5 and it's extremely annoying.
It IS a bug and a big enough bug for me to invoke 'sudo apt-get purge firefox'.
There are times when you simply DO NOT WANT firefox blabbing about
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Hi there,
I did it again. The update-manager gdb session would not crash on me, so
I tried ctrl+C and then the gdb session of the update-manager gdb
session crashed and it did have stack. The update-manager gdb session
itself did not. Also dpkg --configure -a gdb session gave the same (type
off)
ubu...@ubuntu:~$ sudo su
r...@ubuntu:/home/ubuntu# gdb dpkg 21 | tee gdb-dpkg--configure-a.txt
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and
** Attachment added: gdb-gdb.txt
http://launchpadlibrarian.net/21098609/gdb-gdb.txt
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: gdb-gdb-2.log
http://launchpadlibrarian.net/21098612/gdb-gdb-2.log
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: gdb-dpkg--configure-a.txt
http://launchpadlibrarian.net/21098614/gdb-dpkg--configure-a.txt
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: gdb-dpkg--configure-a-2.log
http://launchpadlibrarian.net/21098617/gdb-dpkg--configure-a-2.log
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: update-manager-c-d-6.png
http://launchpadlibrarian.net/21098619/update-manager-c-d-6.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: update-manager-c-d-7.png
http://launchpadlibrarian.net/21098621/update-manager-c-d-7.png
--
update-manager crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
*** This bug is a duplicate of bug 223103 ***
https://bugs.launchpad.net/bugs/223103
** This bug has been marked a duplicate of bug 225312
Chipping sound after playing music ~15 minutes
** This bug is no longer a duplicate of bug 225312
Chipping sound after playing music ~15 minutes
*** This bug is a duplicate of bug 223103 ***
https://bugs.launchpad.net/bugs/223103
** This bug has been marked a duplicate of bug 223103
Multimedia playback broken with pulseaudio and alsa
--
Chipping sound after playing music ~15 minutes
https://bugs.launchpad.net/bugs/225312
You
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = Low
--
Multimedia playback broken with pulseaudio and alsa
https://bugs.launchpad.net/bugs/223103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
pasuspender -- should be used instead.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete = Won't Fix
--
padsp fails
https://bugs.launchpad.net/bugs/218093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
1 - 100 of 1466 matches
Mail list logo
