[Bug 1385114] Re: Panic or segfault in Samba 4.1.6-Ubuntu - but running
Hello - as you were! still appearanche of the panic-message - seems that the outcommand of the above lines has no effect Christoph -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1385114 Title: Panic or segfault in Samba 4.1.6-Ubuntu - but running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1385114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1390752] [NEW] samba wont launch with signal 11
Public bug reported: Not absolutely sure this bug is not already reported due to my insufficient technical abilities. Since installation of Ubuntu 14.10 I can't have a remote access to my computer from lan - tried to open samba but it didn't launch or crashed immediately (asking for password, dialog box closes when it is given and nothing then) - uninstalled, purged and reinstalled samba - same issue. Samba version is included in the log report hereunder (from /var/log/samba/log.%m) : [2014/11/08 17:59:44.320560, 0] ../source4/smbd/server.c:370(binary_smbd_main) samba version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 17:59:44.404857, 0] ../lib/util/util.c:216(directory_create_or_exist) mkdir failed on directory /var/lib/samba/private/smbd.tmp: No such file or directory [2014/11/08 17:59:44.404989, 0] ../lib/util/fault.c:72(fault_report) === [2014/11/08 17:59:44.405021, 0] ../lib/util/fault.c:73(fault_report) INTERNAL ERROR: Signal 11 in pid 950 (4.1.11-Ubuntu) Please read the Trouble-Shooting section of the Samba HOWTO [2014/11/08 17:59:44.405066, 0] ../lib/util/fault.c:75(fault_report) === [2014/11/08 17:59:44.405124, 0] ../lib/util/fault.c:133(smb_panic_default) smb_panic(): calling panic action [/usr/share/samba/panic-action 950] [2014/11/08 17:59:44.476990, 0] ../lib/util/fault.c:141(smb_panic_default) smb_panic(): action returned status 0 [2014/11/08 17:59:44.477074, 0] ../lib/util/fault.c:144(smb_panic_default) PANIC: internal error here is log.smdb : [2014/11/08 17:59:44, 0] ../source3/smbd/server.c:1209(main) smbd version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 17:59:44.729823, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:44.729899, 0] ../source3/smbd/server.c:1289(main) standard input is not a socket, assuming -D option [2014/11/08 17:59:44.750918, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:44.750974, 0] ../lib/util/become_daemon.c:124(exit_daemon) STATUS=daemon failed to start: smbd can not open secrets.tdb, error code 13 [2014/11/08 17:59:45, 0] ../source3/smbd/server.c:1209(main) smbd version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 17:59:45.597845, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:45.597905, 0] ../source3/smbd/server.c:1289(main) standard input is not a socket, assuming -D option [2014/11/08 17:59:45.598167, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:45.598200, 0] ../lib/util/become_daemon.c:124(exit_daemon) STATUS=daemon failed to start: smbd can not open secrets.tdb, error code 13 [2014/11/08 17:59:45, 0] ../source3/smbd/server.c:1209(main) smbd version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 17:59:45.921613, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:45.921717, 0] ../source3/smbd/server.c:1289(main) standard input is not a socket, assuming -D option [2014/11/08 17:59:45.922261, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:45.922306, 0] ../lib/util/become_daemon.c:124(exit_daemon) STATUS=daemon failed to start: smbd can not open secrets.tdb, error code 13 [2014/11/08 17:59:45, 0] ../source3/smbd/server.c:1209(main) smbd version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 17:59:45.975873, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:45.975929, 0] ../source3/smbd/server.c:1289(main) standard input is not a socket, assuming -D option [2014/11/08 17:59:45.976206, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:45.976244, 0] ../lib/util/become_daemon.c:124(exit_daemon) STATUS=daemon failed to start: smbd can not open secrets.tdb, error code 13 [2014/11/08 17:59:46, 0] ../source3/smbd/server.c:1209(main) smbd version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 17:59:46.006277, 0] ../source3/passdb/secrets.c:85(secrets_init_path) Failed to open /var/lib/samba/private/secrets.tdb [2014/11/08 17:59:46.006333, 0] ../source3/smbd/server.c:1289(main) standard input is not a socket, assuming -D option [2014/11/08 17:59:46.006615, 0]
[Bug 1390752] Re: samba wont launch with signal 11
I manually added /var/lib/samba/private/smbd.tmp but it did'nt allow samba to launch instead. The lines below where added to log.%m at reboot : [2014/11/08 18:59:23.013446, 0] ../source4/smbd/server.c:370(binary_smbd_main) samba version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 18:59:25.972830, 0] ../source4/smbd/server.c:475(binary_smbd_main) At this time the 'samba' binary should only be used for either: 'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote' You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks [2014/11/08 18:59:25.972938, 0] ../lib/util/become_daemon.c:124(exit_daemon) STATUS=daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code 22 and the following ones to log.smbd : [2014/11/08 18:59:23, 0] ../source3/smbd/server.c:1209(main) smbd version 4.1.11-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2014/11/08 18:59:23.662299, 0] ../source3/smbd/server.c:1289(main) standard input is not a socket, assuming -D option [2014/11/08 18:59:25.73, 0] ../lib/util/become_daemon.c:136(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connectionsUnable to connect to CUPS server localhost:631 - Bad file descriptor STATUS=daemon 'smbd' finished starting up and ready to serve connectionsfailed to retrieve printer list: NT_STATUS_UNSUCCESSFUL Erik -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1390752 Title: samba wont launch with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1390752/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1390752] Re: samba wont launch with signal 11
This bug looks like #1385854 which has been decided as Invalid since the distro was Ubuntu-mate. Erik -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1390752 Title: samba wont launch with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1390752/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1366174] Re: apache2 SEGV with multiple SSL sites
I have added [Impact] and [Regression potential] sections. Do the SRU requirements mean we need a patch for U too? I'm not sure what current development release means right now given that U is out. I believe the upstream 2.4.10 patch should apply straight to U. It's upstream, so V will presumably get whatever upstream has. I'll ask for someone to nominate this but I think you may need to take it from here, Robie. ** Description changed: Apache2 crashes with multiple SSL sites. + + [Impact] + + Apache may SEGV on initialisation (and thus refuse to start) when using + multiple SSL sites in a moderately complex configuration. Though the + crash is caused by OCSP stapling code, it is not necessary for OCSP to + be enabled to cause the problem. As the problem is caused by a memory + address changing between reads of the config file, in theory any + configuration with one SSL site could refuse to run, though in practice + a degree of complexity appears to be necessary to cause sufficient + memory allocation to trigger the crash. + + The bug is thus serious as any SSL apache configuration may not load. + + [Testcase] + + See comment #1 + + [Regression Potential] + + The most likely regression potential is a failure of OCSP to work + properly. OCSP is relatively new and little used code, and hence is less + well tested than other areas. Though the work was done upstream and has + been approved by OCSP-familiar apache authors, it is possible a change + to the OCSP code will cause some OCSP functionality defect. However, the + comparative lack of use of OCSP (compared to SSL) means the impact of + any such failure should be limited. + + + Detailed description follows: When starting apache2 with multiple SSL sites I get a SEGV like this: (gdb) bt #0 0x705faaf3 in ?? () from /usr/lib/apache2/modules/mod_ssl.so #1 0x729647a6 in int_free_ex_data (class_index=optimized out, obj=0x55af7460, ad=0x55af7488) at ex_data.c:522 #2 0x72a05061 in x509_cb (operation=operation@entry=3, pval=pval@entry=0x7fffc218, it=it@entry=0x72cc0780 X509_it, - exarg=exarg@entry=0x0) at x_x509.c:113 + exarg=exarg@entry=0x0) at x_x509.c:113 #3 0x72a08fea in asn1_item_combine_free (pval=pval@entry=0x7fffc218, it=it@entry=0x72cc0780 X509_it, combine=combine@entry=0) - at tasn_fre.c:173 + at tasn_fre.c:173 #4 0x72a091c5 in ASN1_item_free (val=val@entry=0x55af7460, it=it@entry=0x72cc0780 X509_it) at tasn_fre.c:71 #5 0x72a0514c in X509_free (a=a@entry=0x55af7460) at x_x509.c:141 #6 0x705ee0b8 in ssl_pphrase_Handle (s=s@entry=0x77fc1de0, p=p@entry=0x77fbf028) at ssl_engine_pphrase.c:275 #7 0x705e3658 in ssl_init_Module (p=0x77ff0028, plog=optimized out, ptemp=0x77fbf028, base_server=0x77fc1de0) - at ssl_engine_init.c:194 + at ssl_engine_init.c:194 #8 0x555aa2a9 in ap_run_post_config (pconf=0x77ff0028, plog=0x77fbd028, ptemp=0x77fbf028, s=0x77fc1de0) at config.c:103 #9 0x5558ae07 in main (argc=6, argv=0x7fffe5a8) at main.c:765 This is 100% repeatable. This looks very like: - https://bugzilla.redhat.com/show_bug.cgi?id=1074406 + https://bugzilla.redhat.com/show_bug.cgi?id=1074406 save that I am not using Auth at all. However, ssl itself requires the socache logic, so perhaps it has the same root cause. Disabling a couple of SSL sites normally resolves the problem. What I expected to happen: apache2 to start without SEGV What actually happened: apache2 did not start due to SEGV root@nimtest:/root# lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 root@nimtest:/root# apt-cache policy apache2-bin apache2-bin: - Installed: 2.4.7-1ubuntu4.1 - Candidate: 2.4.7-1ubuntu4.1 - Version table: - *** 2.4.7-1ubuntu4.1 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.4.7-1ubuntu4 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Installed: 2.4.7-1ubuntu4.1 + Candidate: 2.4.7-1ubuntu4.1 + Version table: + *** 2.4.7-1ubuntu4.1 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.4.7-1ubuntu4 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages root@nimtest:/root# dpkg --list | egrep '\b(apache2|libssl|openssl)' ii apache2 2.4.7-1ubuntu4.1 amd64Apache HTTP Server ii apache2-bin 2.4.7-1ubuntu4.1 amd64Apache HTTP Server (binary files and
[Bug 1390768] [NEW] Mouse click position is wrong
Public bug reported: When I click somewhere in the w3m window the cursor is positioned 1 row right and 1 column down from the actual mouse pointer position. This is annoying. For example, x# # if I click the x the cursor moves to the (where I expected it to move to the x). Luckily I managed to work around this by patching the function process_mouse(), with something like if (x 0) x--;. (I don't think this is right, though...) Description:Ubuntu Vivid Vervet (development branch) Release:15.04 w3m: Installed: 0.5.3-19 Candidate: 0.5.3-19 Version table: *** 0.5.3-19 0 500 http://do.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: w3m 0.5.3-19 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 8 13:06:29 2014 InstallationDate: Installed on 2014-10-31 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141029) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: w3m (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Description changed: When I click somewhere in the w3m window the cursor is positioned 1 row - right and 1 column down from the actual cursor position. This is + right and 1 column down from the actual mouse pointer position. This is annoying. For example, x# # if I click the x the cursor moves to the (where I expected it to move to the x). Luckily I managed to work around this by patching the function process_mouse(), with something like if (x 0) x--;. Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 w3m: - Installed: 0.5.3-19 - Candidate: 0.5.3-19 - Version table: - *** 0.5.3-19 0 - 500 http://do.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 0.5.3-19 + Candidate: 0.5.3-19 + Version table: + *** 0.5.3-19 0 + 500 http://do.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: w3m 0.5.3-19 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 8 13:06:29 2014 InstallationDate: Installed on 2014-10-31 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141029) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When I click somewhere in the w3m window the cursor is positioned 1 row right and 1 column down from the actual mouse pointer position. This is annoying. For example, x# # if I click the x the cursor moves to the (where I expected it to move to the x). Luckily I managed to work around this by patching the function - process_mouse(), with something like if (x 0) x--;. + process_mouse(), with something like if (x 0) x--;. (I don't think + this is right, though...) Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 w3m: Installed: 0.5.3-19 Candidate: 0.5.3-19 Version table: *** 0.5.3-19 0 500 http://do.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: w3m 0.5.3-19 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 8 13:06:29 2014 InstallationDate: Installed on 2014-10-31 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141029) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to w3m in Ubuntu. https://bugs.launchpad.net/bugs/1390768 Title: Mouse click position is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/w3m/+bug/1390768/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1390771] [NEW] vim-puppet syntax highlighting scripts are not effective
Public bug reported:
The scripts from vim-puppet are installed to `/usr/share/vim/addons`
which doesn't appear to be used by the current vim distributed with
Ubuntu 14.04. The net effect is that installing the vim-puppet package
seems to do nothing when you edit Puppet scripts.
Here is an example site.pp file:
file { '/etc/motd':
contents = 'Hello, world!',
}
To reproduce:
1. Run vim site.pp
Expected behavior:
Syntax highlighting works. Running :set filetype? reveals that the
filetype is puppet.
Observed behavior:
Syntax highlighting does not work. Running :set filetype? shows there
is no filetype set. On some files, some other script detects the
filetype as conf.
If I run vim site.pp and then :scriptnames this is what I get:
1: /usr/share/vim/vimrc
2: /usr/share/vim/vim74/debian.vim
3: /usr/share/vim/vim74/syntax/syntax.vim
4: /usr/share/vim/vim74/syntax/synload.vim
5: /usr/share/vim/vim74/syntax/syncolor.vim
6: /usr/share/vim/vim74/filetype.vim
7: ~/.vimrc
8: /usr/share/vim/vim74/plugin/getscriptPlugin.vim
9: /usr/share/vim/vim74/plugin/gzip.vim
10: /usr/share/vim/vim74/plugin/matchparen.vim
11: /usr/share/vim/vim74/plugin/netrwPlugin.vim
12: /usr/share/vim/vim74/plugin/rrhelper.vim
13: /usr/share/vim/vim74/plugin/spellfile.vim
14: /usr/share/vim/vim74/plugin/tarPlugin.vim
15: /usr/share/vim/vim74/plugin/tohtml.vim
16: /usr/share/vim/vim74/plugin/vimballPlugin.vim
17: /usr/share/vim/vim74/plugin/zipPlugin.vim
18: /usr/share/vim/vim74/scripts.vim
Since most of these scripts are installed into /usr/share/vim/vim74 I
guessed the files are just in the wrong place. I linked each of the
installed puppet.vim files into their corresponding subdirectory in
`vim74/`. This gets the expected behavior for me.
This is what I get after running vim site.pp and then :scriptnames
after doing this.
1: /usr/share/vim/vimrc
2: /usr/share/vim/vim74/debian.vim
3: /usr/share/vim/vim74/syntax/syntax.vim
4: /usr/share/vim/vim74/syntax/synload.vim
5: /usr/share/vim/vim74/syntax/syncolor.vim
6: /usr/share/vim/vim74/filetype.vim
7: /usr/share/vim/vim74/ftdetect/puppet.vim
8: ~/.vimrc
9: /usr/share/vim/vim74/plugin/getscriptPlugin.vim
10: /usr/share/vim/vim74/plugin/gzip.vim
11: /usr/share/vim/vim74/plugin/matchparen.vim
12: /usr/share/vim/vim74/plugin/netrwPlugin.vim
13: /usr/share/vim/vim74/plugin/rrhelper.vim
14: /usr/share/vim/vim74/plugin/spellfile.vim
15: /usr/share/vim/vim74/plugin/tarPlugin.vim
16: /usr/share/vim/vim74/plugin/tohtml.vim
17: /usr/share/vim/vim74/plugin/vimballPlugin.vim
18: /usr/share/vim/vim74/plugin/zipPlugin.vim
19: /usr/share/vim/vim74/scripts.vim
20: /usr/share/vim/vim74/syntax/puppet.vim
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vim-puppet 3.4.3-1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 8 12:28:14 2014
InstallationDate: Installed on 2014-04-29 (193 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: puppet
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1390771
Title:
vim-puppet syntax highlighting scripts are not effective
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1390771/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-openstack-charms] OpenStack Charm work for Saucy/Havana
Blueprint changed by Adam Gandelman: Assignee: Adam Gandelman = (none) -- OpenStack Charm work for Saucy/Havana https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1316111] Re: mount.cifs task fails to freeze during suspend; suspend fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1316111 Title: mount.cifs task fails to freeze during suspend; suspend fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1316111/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1387510] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvswitch (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1387510 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1387510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Fair enough. I should say that the reason I filed this bug and tried my hand at a fix is so that devstack can just install the qemu-kvm package on any architecture to get enough qemu to make libvirt happy -- devstack/libvirt doesn't use the kvm wrapper script so I only did that bit to keep Adam happy :) (IOW, _I_ would be happy with just this change: https://github.com/mwhudson/qemu/commit/022509bc0cc79fa38bae3b57e947826f10f47ce2 ) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1376927] Re: [SRU] Configurable block device mapping timeout in compute
** Branch linked: lp:~corey.bryant/nova/2014.1.3-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1376927 Title: [SRU] Configurable block device mapping timeout in compute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1376927/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1390847] [NEW] package libboost1.53-tools-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubu
Public bug reported: trying to get openmw running ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libboost1.53-tools-dev (not installed) ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: libboost1.53-tools-dev: Install libboost-tools-dev: Install libboost1.53-tools-dev: Configure libboost-tools-dev: Configure Architecture: i386 Date: Sun Nov 9 00:10:19 2014 DpkgTerminalLog: Unpacking libboost1.53-tools-dev (from .../libboost1.53-tools-dev_1.53.0-6+exp3ubuntu8_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libboost1.53-tools-dev_1.53.0-6+exp3ubuntu8_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubuntu3 DuplicateSignature: package:libboost1.53-tools-dev:(not installed):trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubuntu3 ErrorMessage: trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubuntu3 InstallationDate: Installed on 2013-12-14 (329 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: boost1.53 Title: package libboost1.53-tools-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: boost1.53 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1390847 Title: package libboost1.53-tools-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.53/+bug/1390847/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1390847] Re: package libboost1.53-tools-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubunt
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1390847 Title: package libboost1.53-tools-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bjam.1.gz', which is also in package libboost1.54-dev 1.54.0-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.53/+bug/1390847/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
