[Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a
I have a similar issue, getting these messages from apparmor: May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for /etc/apparmor.d/usr.sbin.nscd in /etc/apparmor.d/tunables/multiarch at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN May 28 06:52:02 bureau apparmor[993]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for /etc/apparmor.d/usr.sbin.smbd in /etc/apparmor.d/tunables/multiarch at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for /etc/apparmor.d/usr.sbin.smbldap-useradd in /etc/apparmor.d/tunables/multiarch at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for /etc/apparmor.d/usr.sbin.tcpdump in /etc/apparmor.d/tunables/multiarch at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for /etc/apparmor.d/usr.sbin.traceroute in /etc/apparmor.d/tunables/multiarch at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN May 28 06:52:02 bureau apparmor[993]:...fail! However, I think the error is deeper than some faulty profiles because no profiles get loaded at all: > sudo aa-status apparmor module is loaded. 0 profiles are loaded. 0 profiles are in enforce mode. 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. Does anybody have a suggestion for how to investigate further? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756800 Title: Failed to start AppArmor initialization with status=123/n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378783] Re: xdg-open *.desktop opens text editor
A very annoying bug, and *Still* not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/378783 Title: xdg-open *.desktop opens text editor To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/378783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770515] Re: The keybind of Unity's launcher conflicts with Magnifier plugin of Compiz
Indeed, it's quite annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770515 Title: The keybind of Unity's launcher conflicts with Magnifier plugin of Compiz To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/770515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406112] [NEW] empathy crashes when opening jabber chat room
Public bug reported:
Empathy crashes as soon as I try to join a jabber chat room. This has
always worked fine.
'lsb_release -rd' :
Description:Ubuntu 14.10
Release:14.10
'apt-cache policy empathy':
empathy:
Installed: 3.8.6-0ubuntu13
Candidate: 3.8.6-0ubuntu13
Version table:
*** 3.8.6-0ubuntu13 0
500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
gdb stacktrace:
(gdb) bt
#0 0x004235ad in roster_window_join_chatroom_menu_activate_cb
(action=optimized out, parameter=optimized out, user_data=0x9044f0)
at empathy-roster-window.c:1291
#1 0x7f1d52e42245 in g_closure_invoke (closure=0x8e7f80, return_value=0x0,
n_param_values=2, param_values=0x7fffac1b2ae0, invocation_hint=0x7fffac1b2a80)
at /build/buildd/glib2.0-2.42.1/./gobject/gclosure.c:768
#2 0x7f1d52e53f3c in signal_emit_unlocked_R (node=node@entry=0x87e560,
detail=detail@entry=0, instance=instance@entry=0x89cac0,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7fffac1b2ae0) at
/build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3553
#3 0x7f1d52e5c748 in g_signal_emit_valist (instance=optimized out,
signal_id=optimized out, detail=optimized out,
var_args=var_args@entry=0x7fffac1b2c70)
at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3309
#4 0x7f1d52e5c9af in g_signal_emit (instance=instance@entry=0x89cac0,
signal_id=optimized out, detail=detail@entry=0)
at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3365
#5 0x7f1d53130ab5 in g_simple_action_activate (action=0x89cac0,
parameter=0xb8dc60) at /build/buildd/glib2.0-2.42.1/./gio/gsimpleaction.c:211
#6 0x7f1d5312f441 in g_action_activate (action=0x89cac0,
parameter=0xb8dc60) at /build/buildd/glib2.0-2.42.1/./gio/gaction.c:390
#7 0x7f1d53c66db5 in gtk_application_window_actions_activate_action_full
(remote=0x8a1210, action_name=0x799560 join, parameter=0xb8dc60,
platform_data=0xb8f790) at
/build/buildd/gtk+3.0-3.12.2/./gtk/gtkapplicationwindow.c:152
#8 0x7f1d5312dc06 in org_gtk_Actions_method_call (connection=optimized
out, sender=optimized out, object_path=optimized out,
interface_name=optimized out, method_name=optimized out,
parameters=0x7f1d2c0246c0, invocation=0x7f1d2c003160, user_data=0x9d06d0)
at /build/buildd/glib2.0-2.42.1/./gio/gactiongroupexporter.c:427
#9 0x7f1d5314fb3c in call_in_idle_cb (user_data=0x7f1d2c003160) at
/build/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:4884
#10 0x7f1d52b6cb6d in g_main_dispatch (context=0x72f350) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3111
#11 g_main_context_dispatch (context=context@entry=0x72f350) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3710
#12 0x7f1d52b6cf48 in g_main_context_iterate
(context=context@entry=0x72f350, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out)
at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3781
#13 0x7f1d52b6cffc in g_main_context_iteration (context=0x72f350,
context@entry=0x0, may_block=may_block@entry=1)
at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3842
#14 0x7f1d531291ac in g_application_run (application=0x73e150,
argc=argc@entry=1, argv=argv@entry=0x7fffac1b31b8)
at /build/buildd/glib2.0-2.42.1/./gio/gapplication.c:2282
#15 0x004165b9 in main (argc=1, argv=0x7fffac1b31b8) at empathy.c:847
(gdb) fr 0
#0 0x004235ad in roster_window_join_chatroom_menu_activate_cb
(action=optimized out, parameter=optimized out, user_data=0x9044f0)
at empathy-roster-window.c:1291
1291 DEBUG (Failed to get chatroom '%s' on '%s': %s,
(gdb) li
1286
1287 chatroom = empathy_chatroom_manager_find
(self-priv-chatroom_manager,
1288 account, room);
1289 if (chatroom == NULL)
1290{
1291 DEBUG (Failed to get chatroom '%s' on '%s': %s,
1292 room, path, error-message);
1293 g_error_free (error);
1294 goto out;
1295}
(gdb) ins room
$1 = (const gchar *) 0x799568 blaat
(gdb) ins path
$2 = (const gchar *) 0x79956e
/org/freedesktop/Telepathy/Account/gabble/jabber/martijn_40bvchitchat1
(gdb) ins error
$3 = (GError *) 0x0
** Affects: empathy (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/1406112
Title:
empathy crashes when opening jabber chat room
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1406112/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264281] [NEW] remote X app crashes local server
Public bug reported: When I ssh to my laptop with X forwarding (ssh -Y or ssh -X) and run thunderbird (and some other apps) it crashes my local X session and it sometimes even crashes the remote X session as well. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.88 Wed Mar 27 14:26:46 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 26 12:26:04 2013 DistUpgraded: 2013-11-15 15:10:02,217 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-13-generic, x86_64: installed nvidia-304, 304.88, 3.11.0-14-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83b5] InstallationDate: Installed on 2012-02-15 (679 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - nvidia_304 (Proprietary, Enabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: OEM Manufacturer MS-7673 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=96dc549b-89c9-48df-b04f-22835a6db995 ro splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to saucy on 2013-11-15 (40 days ago) dmi.bios.date: 04/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P67A-C43 (MS-7673) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd04/14/2011:svnOEMManufacturer:pnMS-7673:pvr1.0:rvnMSI:rnP67A-C43(MS-7673):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7673 dmi.product.version: 1.0 dmi.sys.vendor: OEM Manufacturer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Dec 26 12:15:21 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Wacom Intuos4 4x6 stylus: Invalid type 'touch' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264281 Title: remote X app crashes local server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1264281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175496] [NEW] network-manager forgets the most recently connected networks
Public bug reported: Since I updated to raring ringtail, network-manager forgets which networks to connect to. I have defined several connections in network manager. For example for my wired connection I have one connection named 'home' which uses a static ip, and once named 'work' which uses another static ip, and one named 'dhcp' which uses dhcp. Pre-raring this worked fine, since NM remembered which connection was used last and picked that again, so that If I stay at home and turn on my laptop it will pick the 'home' network each time after I have selected it once. In raring this is different, NM always picks the first connection from the list instead of the conection used last time. This means I have to manually change the network *each time* I connect to a network, instead of only hen I change locations. Tis is not wired network specific: at work we use several different wifi AP's with different names, one for an internal network and one for internet access. I want to connect to the 'internet' AP most of the time, but since the internal is first in the list NM now picks that one each time. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: forgets network-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175496 Title: network-manager forgets the most recently connected networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1175496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096612] [NEW] canon pixma MP970 TPU scanning stopped working
Public bug reported: The scanning with the transparency unit fails consistently with 'operation was cancelled'. I downloaded the source from http://git.debian.org/?p=sane/sane- backends.git and used git bisect to find the first failing commit. The commit causing the bug is 9fc0ac9d1bf771510e11815a9ffad309d29e49d1 Author: Rolf Bensch roben-gu...@alioth.debian.org 2012-04-04 15:15:18 Committer: Rolf Bensch roben-gu...@alioth.debian.org 2012-04-04 15:15:18 Parent: 9c6afe1b95f47de2a9b2dd85b8f4171cc2ea0c93 (cropping y and h to scanable area in TPU mode) Child: d723944fae0875e11e9c0b6147075d1a21b47080 (new scanners Canon Pixma MX510 and Canon Pixma MX890) Branches: master, remotes/origin/master Follows: RELEASE_1_0_22 Precedes: RELEASE_1_0_23 color and grayscale negatives scan in TPU mode for CS8800F and CS9000F I can see there are indeed some changes in the pixma code at this commit, but I don't know enough about the subject to see what's wrong. It would probably be better to report it directly ion the debian bug tracker of the sane project, but I don't feel like creating *yet another* online account just to report a bug. ** Affects: sane-backends (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/1096612 Title: canon pixma MP970 TPU scanning stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1096612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 674138] Re: Global appmenu breaks sloppy focus
FWIW i'd like to let my voice be heard here a well. I *really* like unity so far, except for the FFM problems. I'd very much like an option to have the global menu only on maximized windows, which would solve both the FFM behaviour as make my large monitor more usable with small windows. All the other solutions to the FFM problem seem a bit baroque to me, but maybe they would work better on smallish monitors? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/674138 Title: Global appmenu breaks sloppy focus To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/674138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187540] Re: Gnome-panel freeze when 8 windows are open when the panel is vertical
this bug still happens here on jaunty. I can open 8 windows and then it hangs. The workaround using the separator does work, but it is not a very nice workaround, since I's rather use all of the available vertical space. -- Gnome-panel freeze when 8 windows are open when the panel is vertical https://bugs.launchpad.net/bugs/187540 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 263963] Re: [iwl*] intel drivers take overly long to associate to WPA for some hardware
same here. WPA-PSK /TKIP doesn't work. It keeps asking for a passkey. Also, the passkey entered changes when you try to connect (form OHAKWEPA to 647168370b0c2a3f94cda08aff610611e96d7a0f8d95990df9b6b80b920fc459, or from anything to that string actually. Whatever I type in it always seems to actually use the above 64...59 string or something which looks very much like it) dmesg tells me: [ 2164.977468] eth1: authenticate with AP 00:03:2f:28:f8:7a [ 2164.979219] eth1: authenticated [ 2164.979232] eth1: associate with AP 00:03:2f:28:f8:7a [ 2165.176052] eth1: associate with AP 00:03:2f:28:f8:7a [ 2165.376099] eth1: associate with AP 00:03:2f:28:f8:7a [ 2165.576101] eth1: association with AP 00:03:2f:28:f8:7a timed out I have a feeling the fixed release schedule (april/october) is not working out so well for intrepid, since this is only one of the many regressions I experirenced while upgrading from hardy. -- [iwl*] intel drivers take overly long to associate to WPA for some hardware https://bugs.launchpad.net/bugs/263963 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 293687] [NEW] package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Public bug reported: Binary package hint: update-manager standard upgrade of up-to-date hardy - intrepid ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Package: update-manager 1:0.93.32 PackageArchitecture: all SourcePackage: update-manager Title: package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Uname: Linux 2.6.24-21-generic i686 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/293687 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 293687] Re: package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/19343030/Dependencies.txt ** Attachment added: VarLogDistupgradeAptlog.gz http://launchpadlibrarian.net/19343031/VarLogDistupgradeAptlog.gz ** Attachment added: VarLogDistupgradeApttermlog.gz http://launchpadlibrarian.net/19343032/VarLogDistupgradeApttermlog.gz ** Attachment added: VarLogDistupgradeMainlog.gz http://launchpadlibrarian.net/19343033/VarLogDistupgradeMainlog.gz ** Attachment added: VarLogDistupgradeTermlog.gz http://launchpadlibrarian.net/19343034/VarLogDistupgradeTermlog.gz -- package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/293687 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 157044] Re: slow photo printing since upgrading Feisty to Gutsy
I think it doesn't happen with upstream ghostscript. I seem to remember installing a compiled-from-source ghostscript on a friend's machine fixed the delay. I think the bug is in ubuntu's version. I haven't got the time to test this at the moment (on work computers I cannot install custom stuff). But it might explain ghostscript's reaction. disclaimer: It has been a while and I cannot remember if I installed AFPL or GPL ghostscript. I might be the bug is in the GPL version but not the AFPL version. Th AFPL version is fast, that's for sure. -- slow photo printing since upgrading Feisty to Gutsy https://bugs.launchpad.net/bugs/157044 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 208828] Re: Nautilus folder copy fails with Permission Denied from SMB network share to desktop
I have the same problem here. It won't copy any directory from within nautilus. This might well be a server error, but since I have no possibility to upgrade the firmware of the NAS box it would be quite useful if nautilues would work around it. I know this must be possible because manually issuing a 'cp -R ~/.gvfs/sharedfolder/foldertocopy /tmp' does work, and it copies foldertocopy to /tmp without problems. smbclient //netdisk/shared -c exit gives: Password:pressed enter Domain=[ȇ] OS=[] Server=[���] which doesn't look to helpful ;-) -- Nautilus folder copy fails with Permission Denied from SMB network share to desktop https://bugs.launchpad.net/bugs/208828 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 173900] Re: first part of set titles is interpreted as composer/artist
pity it's not fixable, since it's a rather large annoyance. In my cd collection about 2 of every 3 cd's have errors this way. Too bad freedb uses such a braindead field separating scheme, Why don't they quote/escape their strings ;-( -- first part of set titles is interpreted as composer/artist https://bugs.launchpad.net/bugs/173900 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
Re: [Bug 173900] Re: first part of set titles is interpreted as composer/artist
Ross Burton wrote: On Thu, 2007-12-20 at 11:08 +, marsteegh wrote: pity it's not fixable, since it's a rather large annoyance. In my cd collection about 2 of every 3 cd's have errors this way. Too bad freedb uses such a braindead field separating scheme, Why don't they quote/escape their strings ;-( For every album which appears like this, pressing Disc - Submit should let you associate the CD ID with a track listing. Musicbrainz may have it already with a different ID which means you just have to press another button, or you can import from freedb and fix the titles once and for all. Ross hmm, I have to try how this works. I did submit titles to musicbrains, but found the process fairly unintuitive, and I did't really see a way to choose where to import the titles from, but I'll try. I take it SJ first tries musicbrainz, and then freedb? btw it is a pity that when you submit a disk, it doesn't send all yout painstakingly typed titles to Musicbrainz, and you have to type them all over again on the musicbrainz site. But nothing's perfect I guess ;-) -- first part of set titles is interpreted as composer/artist https://bugs.launchpad.net/bugs/173900 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 173900] Re: first part of set titles is interpreted as composer/artist
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/10725844/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/10725845/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/10725846/ProcStatus.txt -- first part of set titles is interpreted as composer/artist https://bugs.launchpad.net/bugs/173900 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 173900] first part of set titles is interpreted as composer/artist
Public bug reported: Binary package hint: sound-juicer This only happens when sound juicer gets track title/artist information from musicbrainz, not when you manually enter it. When a track has a title +m artist like title:Song1/Song2/Tune3 artist:Artist which is quite common in folk cd's where one tracks consists of a set of multiple tunes/songs. The first part of the title is interpreted as the artist, and overwrites the actual artist, so the above example becomes title: Song2/Tune3 artist: Song1 ProblemType: Bug Architecture: i386 Date: Tue Dec 4 14:25:36 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/sound-juicer NonfreeKernelModules: nvidia Package: sound-juicer 2.20.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: sound-juicer -d /dev/scd0 ProcCwd: /home/martijn ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sound-juicer Uname: Linux martijn-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux ** Affects: sound-juicer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- first part of set titles is interpreted as composer/artist https://bugs.launchpad.net/bugs/173900 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 164193] Re: firestarter firewall doesn't start when the trusted interface is not configured
package version firestarter1.0.3-6ubuntu1 ubuntu 7.10 kernel 2.6.22-14-generic -- firestarter firewall doesn't start when the trusted interface is not configured https://bugs.launchpad.net/bugs/164193 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 164193] firestarter firewall doesn't start when the trusted interface is not configured
Public bug reported: Binary package hint: firestarter I have a ppp connection and an ethernet connection, firestarter is set to start when ppp0 comes up. if the ethernet connection is set to dhcp, but is not connected, firestarted fails to start when ppp0 comes up, claiming eth0 is not configured. This is sort of correct, but it is the wrong behaviour since firestarter not only protects the local network (eth0) but also the computer itself, and should do its job also when no local network cable is plugged in. ** Affects: firestarter (Ubuntu) Importance: Undecided Status: New -- firestarter firewall doesn't start when the trusted interface is not configured https://bugs.launchpad.net/bugs/164193 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 157044] Re: slow photo printing since upgrading Feisty to Gutsy
same here ghostscript is slow as a dog, especially for .ps files containing large bitmaps. The problem is definitely in gs, and not in cups, since gv is also very slow and shows gs running on 99% cpu with ps -A -- slow photo printing since upgrading Feisty to Gutsy https://bugs.launchpad.net/bugs/157044 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
