[Bug 1956029] Re: ufw remains inactive at boot time
Sorted out the issue. I've got systemd to also wait for ufw to load when starting fail2ban. Fail2ban issues a many iptables commands in rapid succession and then it's database of banned IPs is large it takes a considerable amount of time for the firewall to be initialised. In the meanwhile anything issuing iptables commands quite likely fail as is it not possible to have more than one instance of iptables active at any one time. ufw script completes its tasks quickly so makes sense to force that service to start before the fail2ban service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956029 Title: ufw remains inactive at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956029] Re: ufw remains inactive at boot time
Right after reboot I tried to get the status. Result is . . . . root@loki:~# s ufw status ERROR: problem running iptables: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? . . . . while fail2ban is setting up its rules. Anyway... After a reeboot, whatever I've done seems to have worked. I'm assuming adding "ufw.service" to fail2ban.service may have done the trick as has been mentioned on comment 4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956029 Title: ufw remains inactive at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956029] Re: ufw remains inactive at boot time
By networking stops means that I can not establish a connection with the Lemaker BananaPi Pro on any port so I can't get a SSHed shell, can't access the VPN server, etc... It behaves like someone has plugged the network cable. Putting "ufw.service" was a guess, but I've not rebooted the OS yet with that in place. root@loki:~# iptables --version iptables v1.8.4 (legacy) root@loki:~# uname -a Linux loki 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l armv7l armv7l GNU/Linux root@loki:~# fail2ban-client --version Fail2Ban v0.11.1 OS in use obtained from here: https://www.armbian.com/banana-pi-pro/ I will try a reboot and see what happens. Will report result back here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956029 Title: ufw remains inactive at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956029] Re: ufw remains inactive at boot time
root@loki:/home/myron# journalctl -u ufw.service -- Logs begin at Wed 2021-12-29 15:30:45 GMT, end at Thu 2021-12-30 13:10:27 GMT. -- -- No entries -- - Current status of service. ufw was enabled manually so is actually active. It won't be once I reboot. root@loki:/home/myron# systemctl status ufw ● ufw.service - Uncomplicated firewall Loaded: loaded (/lib/systemd/system/ufw.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-12-29 15:30:34 GMT; 21h ago Docs: man:ufw(8) Main PID: 295 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/ufw.service Warning: journal has been rotated since unit was started, output may be incomplete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956029 Title: ufw remains inactive at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956029] Re: ufw remains inactive at boot time
** Description changed: - I was advised to start a bug report: - https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/comments/38 + I was advised to start a bug report (Comment 38): + https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856 I "ufw enable" then several seconds later networking stops. I have get Ubuntu to gracefully power-down using the power-button and then gracefully power-up. Out of curiosity, is anyone here having this problem wish ufw starting up at boot time while also using having fail2ban installed? Here is my theory. It takes a while for fail2ban to issue all the iptable commands to configure the firewall. When ufw tries to initialise there may be a clash or lock held either by an iptables instance spawned by fail2ban or an iptables instance spawned by ufw. One of them will fail and will quite probably mess-up ufw's rules breaking network connectivity. This time I waited for fail2ban to finish establishing its iptables rules before issuing "ufw enable" and this time round network connectivity was not lost. How to I ensure that ufw is fully up and initialised BEFORE the fail2ban service starts? - root@loki:~# ./ufw-diag.sh Has python: pass (binary: python3, version: 3.8.10, py3) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass addrtype (LOCAL): pass addrtype (MULTICAST): pass addrtype (BROADCAST): pass icmp (destination-unreachable): pass icmp (source-quench): pass icmp (time-exceeded): pass icmp (parameter-problem): pass icmp (echo-request): pass == IPv6 == Creating 'ufw-check-requirements6'... done Inserting RETURN at top of 'ufw-check-requirements6'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass icmpv6 (destination-unreachable): pass icmpv6 (packet-too-big): pass icmpv6 (time-exceeded): pass icmpv6 (parameter-problem): pass icmpv6 (echo-request): pass icmpv6 with hl (neighbor-solicitation): pass icmpv6 with hl (neighbor-advertisement): pass icmpv6 with hl (router-solicitation): pass icmpv6 with hl (router-advertisement): pass ipv6 rt: pass All tests passed - root@loki:/lib/systemd/system# cat ufw.service [Unit] Description=Uncomplicated firewall Documentation=man:ufw(8) DefaultDependencies=no Before=network.target After=NetworkManager.service [Service] Type=oneshot RemainAfterExit=yes ExecStart=/lib/ufw/ufw-init start quiet # ExecStartPost=/bin/sleep 10 ExecStop=/lib/ufw/ufw-init stop [Install] WantedBy=multi-user.target - root@loki:/lib/systemd/system# cat fail2ban.service [Unit] Description=Fail2Ban Service Documentation=man:fail2ban(1) After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service ufw.service PartOf=firewalld.service [Service] Type=simple ExecStartPre=/bin/mkdir -p /run/fail2ban ExecStart=/usr/bin/fail2ban-server -xf start # if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local # ExecStart=/usr/bin/fail2ban-server -xf --logtarget=sysout start ExecStop=/usr/bin/fail2ban-client stop ExecReload=/usr/bin/fail2ban-client reload PIDFile=/run/fail2ban/fail2ban.pid Restart=on-failure RestartPreventExitStatus=0 255 [Install] WantedBy=multi-user.target - root@loki:/etc/default# cat ufw # /etc/default/ufw # # Set to yes to apply rules to support IPv6 (no means only IPv6 on loopback # accepted). You will need to 'disable' and then 'enable' the firewall for # the changes to take affect. IPV6=yes # Set the default input policy to ACCEPT, DROP, or REJECT. Please note that if # you change this you will most likely want to adjust your rules. DEFAULT
[Bug 1726856] Re: ufw does not start automatically at boot
@jdstrand I've created a new bug report as you suggested: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956029] Re: ufw remains inactive at boot time
** Summary changed: - ufw does not activate at boot time + ufw remains inactive at boot time -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956029 Title: ufw remains inactive at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956029] [NEW] ufw does not activate at boot time
Public bug reported: I was advised to start a bug report: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/comments/38 I "ufw enable" then several seconds later networking stops. I have get Ubuntu to gracefully power-down using the power-button and then gracefully power-up. Out of curiosity, is anyone here having this problem wish ufw starting up at boot time while also using having fail2ban installed? Here is my theory. It takes a while for fail2ban to issue all the iptable commands to configure the firewall. When ufw tries to initialise there may be a clash or lock held either by an iptables instance spawned by fail2ban or an iptables instance spawned by ufw. One of them will fail and will quite probably mess-up ufw's rules breaking network connectivity. This time I waited for fail2ban to finish establishing its iptables rules before issuing "ufw enable" and this time round network connectivity was not lost. How to I ensure that ufw is fully up and initialised BEFORE the fail2ban service starts? - root@loki:~# ./ufw-diag.sh Has python: pass (binary: python3, version: 3.8.10, py3) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass addrtype (LOCAL): pass addrtype (MULTICAST): pass addrtype (BROADCAST): pass icmp (destination-unreachable): pass icmp (source-quench): pass icmp (time-exceeded): pass icmp (parameter-problem): pass icmp (echo-request): pass == IPv6 == Creating 'ufw-check-requirements6'... done Inserting RETURN at top of 'ufw-check-requirements6'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass icmpv6 (destination-unreachable): pass icmpv6 (packet-too-big): pass icmpv6 (time-exceeded): pass icmpv6 (parameter-problem): pass icmpv6 (echo-request): pass icmpv6 with hl (neighbor-solicitation): pass icmpv6 with hl (neighbor-advertisement): pass icmpv6 with hl (router-solicitation): pass icmpv6 with hl (router-advertisement): pass ipv6 rt: pass All tests passed - root@loki:/lib/systemd/system# cat ufw.service [Unit] Description=Uncomplicated firewall Documentation=man:ufw(8) DefaultDependencies=no Before=network.target After=NetworkManager.service [Service] Type=oneshot RemainAfterExit=yes ExecStart=/lib/ufw/ufw-init start quiet # ExecStartPost=/bin/sleep 10 ExecStop=/lib/ufw/ufw-init stop [Install] WantedBy=multi-user.target - root@loki:/lib/systemd/system# cat fail2ban.service [Unit] Description=Fail2Ban Service Documentation=man:fail2ban(1) After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service ufw.service PartOf=firewalld.service [Service] Type=simple ExecStartPre=/bin/mkdir -p /run/fail2ban ExecStart=/usr/bin/fail2ban-server -xf start # if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local # ExecStart=/usr/bin/fail2ban-server -xf --logtarget=sysout start ExecStop=/usr/bin/fail2ban-client stop ExecReload=/usr/bin/fail2ban-client reload PIDFile=/run/fail2ban/fail2ban.pid Restart=on-failure RestartPreventExitStatus=0 255 [Install] WantedBy=multi-user.target - root@loki:/etc/default# cat ufw # /etc/default/ufw # # Set to yes to apply rules to support IPv6 (no means only IPv6 on loopback # accepted). You will need to 'disable' and then 'enable' the firewall for # the changes to take affect. IPV6=yes # Set the default input policy to ACCEPT, DROP, or REJECT. Please note that if # you change this you will most likely want to adjust your rules. DEFAULT_INPUT_POLICY="DROP" # Set the default output policy to ACCEPT, DROP, or REJECT. Please note that if # you change this you will most likely want to adjust your rules. DEFAULT_OUTPUT_POLICY="ACCEPT" # Set the default forward policy to ACCEPT, DROP or REJECT. Please note that # if you change this you will most likely want to adjust your rules DEFAULT_FORWARD_POLICY="DROP" # Set the default application policy to ACCEPT, DROP, REJECT
[Bug 1726856] Re: ufw does not start automatically at boot
Same problem here. Also when I "ufw enable" then several seconds later networking stops. I have get Ubuntu to gracefully power-down using the power-button and then gracefully power-up. ufw 0.36 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890927] [NEW] Installing ubuntu studio 20.04.1 on Asus TUF706IU-AS76
Public bug reported: I'm trying to install Ubuntu alongside pre-installed Windows on Asus TUF series gaming notebook with AMD CPU and NVIDIA GPU. This system also uses an NVME SSD as the system drive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44 Uname: Linux 5.4.0-42-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Sat Aug 8 23:21:20 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed splash acpi=off nouveau.modeset=0 nvme_core.default_ps_max_latency_us=5500 --- LiveMediaBuild: Ubuntu-Studio 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntustudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890927 Title: Installing ubuntu studio 20.04.1 on Asus TUF706IU-AS76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1890927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
Init error reading from descriptor:Broken pipe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400517] [NEW] Please update Tomcat7 in trusty-security to >= 7.0.55 to enable easier server info hiding
Public bug reported: Tomcat 7.0.55 introduced the ability to more easily hide information leaks by adding some configuration to error valve configurations. Enabling these obfuscations help to minimize information sent out when an error is reached. Please update the trusty-security (& related) versions of tomcat7 to at least 7.0.55 (current version as of 2014-12-08 is 7.0.57) ** Affects: tomcat7 (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/1400517 Title: Please update Tomcat7 in trusty-security to >= 7.0.55 to enable easier server info hiding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1400517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211294] [NEW] Crash during 13.04 install, after manually creating partitions.
Public bug reported: Crash when installing Ubuntu. Manual partitioning. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CasperVersion: 1.331 Date: Mon Aug 12 07:01:16 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages ubiquity-2.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211294 Title: Crash during 13.04 install, after manually creating partitions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1211294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987182] Re: apt 403 Forbidden on some packages
This appears to have cropped up again. `apt-get source imagemagick`
fails with a 403 from us-east-1.ec2.archive.ubuntu.com ("west" fails in
the same way). `apt-get clean` and `apt-get update` doesn't resolve the
issue. I have the pipelining fix in place on 12.04.1 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987182
Title:
apt 403 Forbidden on some packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/s3aptmirror/+bug/987182/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763228] Re: amarok crashed with SIGSEGV in Meta::MediaDeviceTrack::prettyUrl()
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763228 Title: amarok crashed with SIGSEGV in Meta::MediaDeviceTrack::prettyUrl() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763228] [NEW] amarok crashed with SIGSEGV in Meta::MediaDeviceTrack::prettyUrl()
Public bug reported: Binary package hint: amarok Any time an iPhone 3G running Whited00r custom firmware connects to the PC, upon clicking "local" in Amarok, Amarok crashes. Also, neither Amarok nor Rhythmbox will play music from the iPod. I am using the Kubuntu Natty daily from 4/16 and have done all available system updates ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: amarok 2:2.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 CrashCounter: 1 Date: Sat Apr 16 19:46:29 2011 ExecutablePath: /usr/bin/amarok InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110416) ProcCmdline: /usr/bin/amarok ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x779b2a:mov%esi,(%esp) PC (0x00779b2a) ok source "%esi" ok destination "(%esp)" (0xbf5a2fe0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: amarok StacktraceTop: ?? () from /usr/lib/libkdecore.so.5 Meta::MediaDeviceTrack::prettyUrl() const () from /usr/lib/libamaroklib.so.1 Meta::Track::prettyName() const () from /usr/lib/libamarokcore.so.1 Meta::MediaDeviceTrack::prettyUrl() const () from /usr/lib/libamaroklib.so.1 Meta::Track::prettyName() const () from /usr/lib/libamarokcore.so.1 Title: amarok crashed with SIGSEGV in Meta::MediaDeviceTrack::prettyUrl() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: amarok (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763228 Title: amarok crashed with SIGSEGV in Meta::MediaDeviceTrack::prettyUrl() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545693] Re: Audio wont play
I can't seem to cancel this bug. Issue was with Pulseaudio. It is repaired now. -- Audio wont play https://bugs.launchpad.net/bugs/545693 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 569032] Re: Evolution + mapi = crash on startup in Lucid
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/45107497/Dependencies.txt -- Evolution + mapi = crash on startup in Lucid https://bugs.launchpad.net/bugs/569032 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569032] [NEW] Evolution + mapi = crash on startup in Lucid
Public bug reported: Binary package hint: evolution-mapi Running Lucid with the latest updates I tried to start evolution this morning and the screen appeared and immediately went away. Executing evolution from the command line I got the following error: exchange-mapi-connection.c:124: Entering mapi_profile_load If I remove the evolution-mapi project, evolution will start. I renamed my ~/.evolution directory and it didn't make any difference. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evolution-mapi 0.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Fri Apr 23 08:43:10 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: evolution-mapi ** Affects: evolution-mapi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug evolution i386 lucid mapi -- Evolution + mapi = crash on startup in Lucid https://bugs.launchpad.net/bugs/569032 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566791] Re: contacts are added and blocked. will not unblock
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44832275/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/44832276/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/44832277/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/44832278/XsessionErrors.txt -- contacts are added and blocked. will not unblock https://bugs.launchpad.net/bugs/566791 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenetwork in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 566791] [NEW] contacts are added and blocked. will not unblock
Public bug reported: Binary package hint: kdenetwork Msn contacts when added, are blocked. and will not unblock when selected. ProblemType: Bug Architecture: i386 Date: Mon Apr 19 09:45:32 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/kopete InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: kopete 4:4.3.2-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: kdenetwork Uname: Linux 2.6.31-20-generic i686 ** Affects: kdenetwork (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- contacts are added and blocked. will not unblock https://bugs.launchpad.net/bugs/566791 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenetwork in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 561387] Re: 2..32-20 kernel locks up on boot in less then a second
Similar problem this morning on my Thinkpad T-60. There is a stack trace on the screen that ends with "[0.345007] [(c0104887)] ? kernel_thread_helper +0x7/0x10. After that is a code (three lines of hex codes), EIP (acpi_ex_read_data_from_field+0x131/0x168 SS:ESP 0060:f6835d70), CR2 (a lot of 0s followed by 9) then a list of the drives on my system. I took a photo of the screen, but I could not find anything in the logs. -- 2..32-20 kernel locks up on boot in less then a second https://bugs.launchpad.net/bugs/561387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545693] Re: Audio wont play
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/41799968/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/41799969/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/41799970/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/41799971/XsessionErrors.txt -- Audio wont play https://bugs.launchpad.net/bugs/545693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545693] [NEW] Audio wont play
Public bug reported: Binary package hint: amarok NO problems with audio card. Youtube plays audio fine, but amorok will not ProblemType: Bug Architecture: i386 Date: Tue Mar 23 20:30:19 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/amarok InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: amarok 2:2.2.0-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: amarok Uname: Linux 2.6.31-14-generic i686 ** Affects: amarok (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Audio wont play https://bugs.launchpad.net/bugs/545693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384955] Re: ISW RAID freezes for minutes at a time
I upgraded my kernel to 2.6.29-5 yesterday and have not had a single freeze since then so there appears to be a fix in that kernel version. -- ISW RAID freezes for minutes at a time https://bugs.launchpad.net/bugs/384955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384955] Re: ISW RAID freezes for minutes at a time
** Attachment added: "Output of "lspci -vvv"" http://launchpadlibrarian.net/27659302/lspciv.out -- ISW RAID freezes for minutes at a time https://bugs.launchpad.net/bugs/384955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384955] [NEW] ISW RAID freezes for minutes at a time
Public bug reported: I received a brand new workstation (Dell Optiplex 960 with dual 360 gig HDs running on an onboard RAID controller) and installed Jaunty x64 on it last week using the alternate CD. Since that time I have experienced random freezes of my machine. It appears to be an issue with the built- in isw RAID. The machine doesn't totally lock up (I can move the mouse, access menus, etc.), but anything related to hard drive activity completely stops. I have noticed this in Firefox, Thunderbird, and Eclipse. Compiz will grey the windows indicating they are not responding and they will not take keystrokes. Typing "ls" at a command prompt will just sit there. After a period of time (usually several minutes) the machine will resume as if nothing happened. I checked my log files and cannot find anything logged when this happens. It is not an issue of memory, the machine has 8 gig on board and only about a third in use most of the time. I have not found a consistent pattern to cause the issue. ** Affects: ubuntu Importance: Undecided Status: New -- ISW RAID freezes for minutes at a time https://bugs.launchpad.net/bugs/384955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 242027] Re: bug to be reported against update manager
** Attachment added: "main.log" http://launchpadlibrarian.net/15503726/main.log ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/15503727/Dependencies.txt ** Attachment added: "VarLogDistupgradeAptlog.gz" http://launchpadlibrarian.net/15503728/VarLogDistupgradeAptlog.gz ** Attachment added: "VarLogDistupgradeApttermlog.gz" http://launchpadlibrarian.net/15503729/VarLogDistupgradeApttermlog.gz ** Attachment added: "VarLogDistupgradeMainlog.gz" http://launchpadlibrarian.net/15503730/VarLogDistupgradeMainlog.gz ** Attachment added: "VarLogDistupgradeTermlog.gz" http://launchpadlibrarian.net/15503731/VarLogDistupgradeTermlog.gz -- bug to be reported against update manager https://bugs.launchpad.net/bugs/242027 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 242027] [NEW] bug to be reported against update manager
Public bug reported: Binary package hint: samba samba not upgraded because of prior modifications to samba ProblemType: Package Architecture: i386 Date: Sat Jun 21 19:30:30 2008 DistroRelease: Ubuntu 8.04 ErrorMessage: ErrorMessage: subprocess post-installation script returned error exit status 1 Package: samba-common 3.0.28a-1ubuntu4.2 PackageArchitecture: i386 SourcePackage: samba Title: package samba-common 3.0.28a-1ubuntu4.2 failed to install/upgrade: Uname: Linux 2.6.24-19-generic i686 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: Triaged ** Tags: apport-package -- bug to be reported against update manager https://bugs.launchpad.net/bugs/242027 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34199] Re: Evolution cannot connect to Exchange backend process
I think they broke it again in the last couple of updates. Today I cannot get Evolution to keep its connection more than a few minutes. Yesterday it worked most of the day. I enabled pre-release updates and even that is not helping now. Every few weeks I'm on support and get added to a couple of different mailing lists. Yesterday I came in after the weekend and had about 6800 messages in my inbox. I have been working ever since to get the filters to run long enough to clear them out. Yesterday I let it run all day and it slowly worked its way through and had about 1500 when I walked in. I have restarted many times so far today and each time it seems to crash faster than the previous restart. Earlier I was getting about 60 messages at a time, now it crashes after about 15 messages (about 2 minutes). I guess that's what I get for accepting updates to Evolution :( -- Evolution cannot connect to Exchange backend process https://bugs.launchpad.net/bugs/34199 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112220] Re: "Connect to Server" attempts connect in background
Once I removed the files, the problem never recurred, so yes, it did fix the problem. -- "Connect to Server" attempts connect in background https://bugs.launchpad.net/bugs/112220 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112220] Re: "Connect to Server" attempts connect in background
The problem has continued today despite my best efforts to solve it. I came very close to removing samba and smbclient, but I may have found something. In my .nautilus/metadata folder, there are a bunch of smb* files. I deleted those files hoping that will stop Nautilus from attempting to connect to those network shares. -- "Connect to Server" attempts connect in background https://bugs.launchpad.net/bugs/112220 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112220] "Connect to Server" attempts connect in background
Public bug reported: I think I have finally tracked down the most irritating problem I have had under Feisty so far. Several times a day my network password has been getting revoked since upgrading. Today I ran wireshark and searched through the packet dump. I found several SMB ACCESS_DENIED and ACCOUNT_LOCKED_OUT messages within the output. The messages were coming from multiple servers I had originally entered into the Places->Connect to Server option as Windows Shares under Edgy. It appears that the system is attempting to connect to these servers even though I have not clicked the icons or made any attempt to use those shares. There is never a password prompt so I do not know what password it is attempting to use, but it must be using the correct user id. I have removed all passwords from my keyring that specify my network user id. When my account got locked out this morning, I only saw an SMB handshake with one ACCESS_DENIED message followed shortly by ACCOUNT_LOCKED_OUT to only one server within the 10 minute period I was monitoring. Shortly after firing up wireshark, I verified my password was working. Before stopping wireshark, I verified my account was locked out. As far as I have been able to discover, these SMB packets are causing my network id to get revoked. After seeing these messages I unmounted all of the network shares I had mapped, but have not rebooted since and the messages continue to appear so it must still be attempting to connect to those severs. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- "Connect to Server" attempts connect in background https://bugs.launchpad.net/bugs/112220 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
