[Touch-packages] [Bug 424655] Re: using module-udev-detect leaks memory

[Bug Watch Updater]

** Changed in: pulseaudio (Fedora)
   Status: Unknown => Fix Released

** Changed in: pulseaudio (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/424655

Title:
  using module-udev-detect leaks memory

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in pulseaudio source package in Karmic:
  Fix Released
Status in udev source package in Karmic:
  Invalid
Status in pulseaudio package in Fedora:
  Fix Released

Bug description:
  --- SRU report follows ---
  Impact: Users of Ubuntu 9.10 may experience a local denial of service 
condition where the PulseAudio daemon process(es) exhausts available memory. 
This is caused by the default-used module-udev-detect not properly freeing 
invalid udev contexts.

  Fixed in 10.04: addressed in the latest Lucid source upload that
  contains the upstream fix

  Minimal fix for 9.10:
  http://launchpadlibrarian.net/37963834/pulseaudio_0.9.19-0ubuntu4.1.debdiff

  TEST CASE: On some configurations, this symptom is immediately
  triggerable. On others, it requires that the user choose a non-stereo
  multichannel profile in System > Preferences > Sound > Hardware >
  Profile

  Regression potential: low -- the existing upstream fix has been well-
  tested in Daniel T Chen's PPA and only touches the relevant code in
  module-udev-detect. The existing workaround of using module-detect
  will not be affected.

  --- Original report follows ---

  Binary package hint: pulseaudio

  Pulse audio routinely uses 2GB+ over the course of a few hours.

  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  pulseaudio:
    Installed: 1:0.9.16~test6-3-g57e1-0ubuntu2
    Candidate: 1:0.9.16~test6-3-g57e1-0ubuntu2
    Version table:
   *** 1:0.9.16~test6-3-g57e1-0ubuntu2 0
  500 http://mirror.optus.net karmic/main Packages
  100 /var/lib/dpkg/status

  I expect pulseaudio to continue to use a couple MB of memory,
  certainly less then 2GB.

  After a few hours of listening to music and the odd youtube video
  pulseaudio ends up with 2GB+ of memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/424655/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 533636] Re: ibus languagebar doesn't show MenuItem on menu.

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=552796.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-01-06T07:03:38+00:00 fujiwara wrote:

I'd like to add MenuItem on ibus languagebar with bug 550001.

Currently ibus supports CheckMenuItem() and RadioMenuItem() but it seems
ImageMenuItem() doesn't work.

When I apply the patch on bug 550001, ibus puts an error:
ibus.Menu receives type == ibus.PROP_TYPE_NORMAL and call 
gtk.ImageMenuItem(prop)
but the argument is not correct.
I'm attaching the patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/0


On 2010-01-06T07:05:38+00:00 fujiwara wrote:

Created attachment 381928
Patch for ibus menu.py

Attached the patch.
It seems to get an error when gtk.ImageMenuItem.__init__() is called so I 
removed it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/1


On 2010-01-06T08:48:45+00:00 fujiwara wrote:

Comment on attachment 381928
Patch for ibus menu.py

>diff --git a/ui/gtk/menu.py b/ui/gtk/menu.py

One typo. Both icon and label can be shown:

  self.set_image(icon.IconWidget(prop.icon, size[0]))
-+elif self._prop.label:
++if self._prop.label:
 +self.set_property("label", prop.label.get_text())

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/2


On 2010-01-07T03:44:26+00:00 fujiwara wrote:

Put ibus-anthy for ImageMenuItem:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1906442

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/3


On 2010-01-07T04:22:06+00:00 fujiwara wrote:

F11 pygtk2 had a problem:
http://git.gnome.org/browse/pygtk/commit/?id=fbb3e653ab1c4f467d7aae61e8444fab8c839af1
--- a/gtk/gtk.override
+++ b/gtk/gtk.override
@@ -2064,24 +2066,20 @@ _wrap_gtk_image_menu_item_new(PyGObject *self, PyObject 
*args,PyObject *kwargs)
-
- if (pyg_type_from_object((PyObject *) self) != GTK_TYPE_IMAGE_MENU_ITEM) {
- PyErr_SetString(PyExc_RuntimeError, "__gobject_init__ must be used "
- "when subclassing gtk.ImageMenuItem");
- return -1;
- }
-
- pygobject_register_wrapper((PyObject *)self);

The previous pygtk sent the error: "__gobject_init__ must be used when
subclassing gtk.ImageMenuItem".

But I confirmed f12 _gtk.so is fixed so this part is not needed now.
I logged this issue for the reference.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/4


On 2010-01-07T05:15:26+00:00 Peng wrote:

Fixed in upstream. I will build it soon.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/5


On 2010-01-11T06:49:37+00:00 Peng wrote:

Fixed in ibus-1.2.0.20100111-1.fc13

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/6


** Changed in: ibus (Fedora)
   Status: Unknown => Fix Released

** Changed in: ibus (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/533636

Title:
  ibus languagebar doesn't show MenuItem on menu.

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Lucid:
  Fix Released
Status in ibus package in Fedora:
  Fix Released

Bug description:
  Binary package hint: ibus

  Newest ibus-anthy doesn't show some icons.
  This is as same as https://bugzilla.redhat.com/show_bug.cgi?id=552796.

  Please apply the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1425447] Re: pulseaudio crashed with SIGABRT in core_free() at login

[Bug Watch Updater]

Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1194177.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-02-19T09:33:02+00:00 Lubomir wrote:

Version-Release number of selected component:
pulseaudio-6.0-1.fc22

Additional info:
reporter:   libreport-2.3.0
backtrace_rating: 4
cmdline:/usr/bin/pulseaudio --start --log-target=syslog
crash_function: core_free
executable: /usr/bin/pulseaudio
kernel: 3.20.0-0.rc0.git6.1.fc22.x86_64
runlevel:   N 5
type:   CCpp
uid:42

Truncated backtrace:
Thread no. 1 (2 frames)
 #2 core_free at pulsecore/core.c:179
 #3 pa_core_unref at pulsecore/core.h:202

Potential duplicate: bug 714401

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/0


On 2015-02-19T09:33:05+00:00 Lubomir wrote:

Created attachment 993499
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/1


On 2015-02-19T09:33:06+00:00 Lubomir wrote:

Created attachment 993501
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/2


On 2015-02-19T09:33:08+00:00 Lubomir wrote:

Created attachment 993503
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/3


On 2015-02-19T09:33:10+00:00 Lubomir wrote:

Created attachment 993504
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/4


On 2015-02-19T09:33:11+00:00 Lubomir wrote:

Created attachment 993505
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/5


On 2015-02-19T09:33:12+00:00 Lubomir wrote:

Created attachment 993506
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/6


On 2015-02-19T09:33:14+00:00 Lubomir wrote:

Created attachment 993507
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/7


On 2015-02-19T09:33:15+00:00 Lubomir wrote:

Created attachment 993509
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/8


On 2015-02-19T09:33:17+00:00 Lubomir wrote:

Created attachment 993511
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/9


On 2015-02-19T09:33:18+00:00 Lubomir wrote:

Created attachment 993512
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/10


On 2016-07-19T12:50:03+00:00 Fedora wrote:

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/30


** Changed in: pulseaudio (Fedora)
   Status: Unknown => Won't Fix

** Changed in: pulseaudio (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1425447

Title:
  pulseaudio crashed with SIGABRT in core_free() at login

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio package in Fedora:
  Won't Fix

Bug description:
  When I login, I get no sound, a "Dummy Output" device which is not
  functional, and then an 

[Touch-packages] [Bug 79078] Re: Receive hangs regularly

[Bug Watch Updater]

Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=217568.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2006-11-28T18:05:55+00:00 John wrote:

Description of problem:
After using evolution for a while, I get to a point when I can no longer send
mail.  Clicking on "Send/Recieve" hangs waiting for the SMTP transaction to
complete, which doesn't.  I attached a screenshot of that dialog.  Trying to
quit out of evolution at this point just hangs.  killall evolution is the only
way out.

Version-Release number of selected component (if applicable):


How reproducible:
2 for 2 so far since installing RHEL5 Beta2

Steps to Reproduce:
1. start evolution
2. use for a while
3. click "send/receive" and watch the SMTP send "waiting"
  
Actual results:
no mail gets sent;

Expected results:


Additional info:

So, to get out of this, one must quit evolution. BUT, evolution hangs exiting.
killall evolution.  Upon restart, sending mail works again.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/0


On 2006-11-28T18:05:55+00:00 John wrote:

Created attachment 142312
screenshot of the send/receive popup

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/1


On 2006-11-29T14:56:06+00:00 John wrote:

I'm finding myself having to "killall evolution" at least 6 times a day now. 
I'd say that's a useability issue.  Probably something that needs to get fixed
before we ship IMHO.  Setting blocker to ?


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/79078/comments/2


On 2006-11-29T15:14:30+00:00 Rod wrote:

I have this issue constantly also.  Beta2.

It is worth noting that I have other issues with evolution (every quit causes a
crash and bug buddy pops up, find contacts does not work by any field, etc.)

I will open other bzs on those



Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/79078/comments/3


On 2006-12-15T14:52:25+00:00 Matthias wrote:

*** Bug 219719 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/4


On 2006-12-15T16:08:21+00:00 Tim wrote:

As described in Bug 219819, I can trigger this pretty readily on some machines
by performing two send/receives in quick succession or by performing a
send/receive right after a single mail send. In other words, the problem occurs
immediately instead of after a few hours.

For what it's worth, the fedora evolution has, so far, not shown me this
error.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/5


On 2007-01-08T17:20:43+00:00 Matthew wrote:

I found a couple similar upstream bugs, but there's been no progress on either
of them.  One was from an Ubuntu user.

http://bugzilla.gnome.org/show_bug.cgi?id=382540
http://bugzilla.gnome.org/show_bug.cgi?id=384183

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/6


On 2007-01-09T12:15:12+00:00 Alexander wrote:

Its also mentioned in:
http://bugzilla.gnome.org/show_bug.cgi?id=317213

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/7


On 2007-01-09T12:17:36+00:00 Alexander wrote:

Corresponding for fc6 is bug 208724

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/8


On 2007-01-10T14:09:18+00:00 Alexander wrote:

Created attachment 145255
Fix for EMsgPort race

I figured this out. Its a race condition in the new EMsgPort implementation.
e_msgport_wait() saves the message in msgport->cache and returns it later in
e_msgport_get(). However, two threads can end up running e_msgport_wait() (if
two threads are waiting and two messages are put), which will result in cache
being overwritten with the last message.

This patch fixes it by making cache a list.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/9

[Touch-packages] [Bug 511558] Re: skype has lag after 0.9.21+stable-queue-24-gfa64

[Bug Watch Updater]

** Changed in: pulseaudio (Fedora)
   Status: Unknown => Fix Released

** Changed in: pulseaudio (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/511558

Title:
  skype has lag after 0.9.21+stable-queue-24-gfa64

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio package in Fedora:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I believe it was always fine with 1:0.9.21-0ubuntu6, but after
  upgrading to 0.9.22~0.9.21+stable-queue-24-gfa64-0ubuntu1 I get a a
  few seconds input lag in Skype.

  1:0.9.21-0ubuntu6 GOOD
  1:0.9.22~0.9.21+341-g62bf-0ubuntu1 GOOD
  0.9.22~0.9.21+stable-queue-24-gfa64-0ubuntu1 BAD
  0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu1 BAD

  The above tests was done without rebooting, so if pulseaudio does not
  restart cleanly when upgrading packages, the above result might be
  skewed. It can also appear intermittently on the second version at
  least: Once it was bad on the second call, but good on first, 3rd-4th-
  5th, another time bad on the first, but good on 2nd-3rd-4th, then
  after leaving it for some minutes, it was bad on the first call again,
  but good in the next.

  The tests were done with skype 2.1.0.81 (from upstream skype-ubuntu-
  intrepid_2.1.0.81-1_i386.deb) but it was the same pattern with
  2.1.0.47.

  TEST CASE:
  Call echo123 "Skype Testing Service" and open the DTMF pad and push some 
buttons.
  Expected: The tone is heard as soon as the button is pressed
  Happening: The tone is heard after several seconds of delay

  (The lag is of course very noticeable in a normal conversation, but
  the DTMF pad is an easy way to test)

  Possibly related upstream bug:
  https://bugzilla.redhat.com/show_bug.cgi?id=554929

  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tormod 1573 F pulseaudio
   /dev/snd/controlC1:  tormod 1573 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xc800 irq 16'
     Mixer name : 'Realtek ALC880'
     Components : 'HDA:10ec0880,0880,00090500 
HDA:11c13026,11c13026,00100600'
     Controls  : 39
     Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x9a2'/'USB Device 0x46d:0x9a2 at usb-:00:1d.7-7, high 
speed'
     Mixer name : 'USB Mixer'
     Components : 'USB046d:09a2'
     Controls  : 2
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
     Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
     Capture channels: Mono
     Limits: Capture 0 - 3072
     Mono: Capture 0 [0%] [18.00dB] [on]
  Date: Sat Jan 23 13:56:51 2010
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+341-g62bf-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.32-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/511558/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1705870] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[James M Knock]

Not virtual. Occurs a few minutes after boot.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1705870

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Sat Jul 22 00:19:41 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-03-25 (849 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x558cc4bc3f20, argc=1, argv=0x7ffe6962b198, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe6962b188) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-yakkety
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-yakkety
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705870/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1581772] Re: Cannot install Epson L355

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1581772

Title:
  Cannot install Epson L355

Status in cups package in Ubuntu:
  Expired

Bug description:
  After upgrade (15.10 > 16.04) my printer dont work. I tried many solutions - 
like install
  lsb or install printer-driver-escpr or reinstall cups.
  even if I added the printer in the system, he still remains silent and does 
not print. Although everything looked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 14 17:07:04 2016
  InstallationDate: Installed on 2015-12-07 (158 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-lowlatency 
root=UUID=5fdb3a85-83cf-4c64-8ef4-c2e35c35f606 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990XA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1581772/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1705127] Re: GTK bubble menu arrows have jaggies when not pointing straight up

[Launchpad Bug Tracker]

[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1705127

Title:
  GTK bubble menu arrows have jaggies when not pointing straight up

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  If you check the balloon arrow in the picture (just below the Save
  button) you can see as that part is very blurry compared to the other
  parts of the balloon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:50:47 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1705127/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 67188] Re: "Error activating XKB configuration." - Requires manual xorg.conf editing

[Bug Watch Updater]

Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446684.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-05-15T17:00:10+00:00 Eelco wrote:

Description of problem:
[Actually, the problem occurs in gnome-keyboard-properties, but that one was not
in the components list.]
Choosing keyboard layout Macbook/Macbook Pro (Intl) produces an error in Fedora 
9. 

Version-Release number of selected component (if applicable):
GNOME gnome-keyboard-properties 2.22.1

How reproducible:
1. start gnome-keyboard-properties
2. select layouts tab
3. select keyboard model MacBook/MacBook Pro (Intl)
4. close

Error message:
==
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10499901

If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd



Additional info:

Hardware: Macbook (late 2006 model)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/36


On 2008-05-15T17:00:10+00:00 Eelco wrote:

Created attachment 305510
screenshot of the error message

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/37


On 2008-05-17T08:31:35+00:00 Eelco wrote:

$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "intl", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "intl", ""

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model = macbook79
 options = [Compose key compose:rwin]
 overrideSettings = true



Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/38


On 2008-05-17T13:05:12+00:00 Lubomir wrote:

Eelco: Thank you for reporting the problem, I am reassigning it to the right
component owner.

The following command might be useful to find out which component does the
binary belong to:

$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/39


On 2008-05-17T13:08:02+00:00 Eelco wrote:

$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)
control-center


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/40


On 2008-05-22T23:29:09+00:00 Jose wrote:

I'm having the same problem (MacBook with a Portuguese keyboard layout):

$ xprop -root | grep  XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "pt", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "pt", "", ""

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [pt  mac,pt]
 model = macbook79
 options = [grp grp:alts_toggle]
 overrideSettings = true

/jpo


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/41


On 2008-09-11T12:33:50+00:00 Peter wrote:

Eelco:

The problem is that the keysyms for mac don't provide a intl variant. The error 
can be reproduced on the commandline by running:
setxkbmap -layout us -model macbook79 -variant intl -print | xkbcomp - :0

Error:No Symbols named "intl" in the include file 
"macintosh_vndr/us"
  Exiting

If this used to work, or you think it should work, please file a bug on
upstream bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product
=xkeyboard-config

Jose:
I can't reproduce your problem. Can you try to run:
setxkbmap -layout pt -model macbook79 -option grp:alts_toggle -print | xkbcomp 
- :0
and check for an error message. If there is one, please attach it. If there is 
none, please try if the macbook79 model works with any other layout (e.g. us). 
If it does, please try to find which setting triggers the error - it could be 
the layout or the alts_toggle option (unlikely).

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/44


On 2008-10-20T21:33:16+00:00 Matěj wrote:

Reporter, could you please reply to the previous question? If you won't
reply in 

[Touch-packages] [Bug 180179] Re: [PATCH] Fix nspr warnings with -Wstrict-prototypes

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451616.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-06-16T08:04:25+00:00 Dan wrote:

Description of problem:
Using nspr header gives a warning in the prlink.h file when -Wstrict-prototypes
is included in the CFLAGS. And when -Werror is used, then it is not possible to
compile at all.

Version-Release number of selected component (if applicable):
nspr-devel-4.6.7-3.fc8
but the header was not changed since Apr/06/2006, so all current Fedora and RHEL
versions are affected.

How reproducible:
100%

Steps to Reproduce:
1. run the script from attachments
  
Actual results:
In file included from /usr/include/nspr4/nspr.h:55,
 from nspr-test.c:2:
/usr/include/nspr4/prlink.h:52: warning: function declaration isn’t a prototype
/usr/include/nspr4/prlink.h:209: warning: function declaration isn’t a prototype


Expected results:
No warnings

Additional info:
There was a thread in gcc mailing list about the meaning of the warning -
http://gcc.gnu.org/ml/gcc-help/2006-07/msg00033.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/8


On 2008-06-16T08:04:25+00:00 Dan wrote:

Created attachment 309468
test case

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/9


On 2008-06-16T08:08:50+00:00 Dan wrote:

Created attachment 309471
patch to remove the warnings

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/10


On 2008-07-01T13:33:41+00:00 Kai wrote:

Wan-Teh, what do you think about the proposed patch?

I should probably file an upstream bug.


Reply at: https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/11


On 2008-11-26T10:52:33+00:00 Bug wrote:


This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/20


On 2009-01-09T06:36:21+00:00 Bug wrote:


Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/23


On 2010-08-16T14:40:02+00:00 Elio wrote:

See https://bugzilla.mozilla.org/show_bug.cgi?id=410677
When we next re-base to NSPR 4.8.6 we will pick-up the fix.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/38


** Changed in: nspr (Fedora)
   Status: Won't Fix => Fix Released

** Changed in: nspr (Fedora)
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nspr in Ubuntu.

[Touch-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446631.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-05-15T14:05:51+00:00 Tom wrote:

Description of problem:

The traditional way to provide information which cannot be provided by
DHCP (specifically in my case additional DNS domain names in search path)
has been by writing an /etc/dhclient-exit-hooks script which can be used
to edit the /etc/resolv.conf file after it is created by DHCP. This script
is no longer being run when NetworkManager creates resolv.conf

Version-Release number of selected component (if applicable):

NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64

How reproducible:

Every time I boot.

Steps to Reproduce:
1. Boot system, observe NetworkManager generated resolv.conf does not
   have the changed dhclient-exit-hooks would have made.
  
Actual results:

see above

Expected results:

augmented search path in resolv.conf

Additional info:

I'd be happy to learn the "new way" to achieve the same thing
dhclient-exit-hooks did, but on the other hand, I'd really wonder
why there would need to be a "new way" other than obsessive OCD
on the part of developers. How hard is it to just run the dadgum
script if it exists?

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/293139/comments/0


On 2008-05-18T22:51:47+00:00 Todd wrote:

NetworkManager provides its own hooks into dhclient so that it can do its thing.
 You can get NetworkManager to call your script though.  NetworkManager runs all
scripts that are in /etc/NetworkManager/dispatcher.d.  There should be at least
one script in there to show you how things work. 

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/293139/comments/1


On 2008-07-10T18:51:02+00:00 Mike wrote:

Scripts in /etc/NetworkManager/dispatcher.d/ do work, but they don't fully
handle the sorts of things the dhclient-script and friends did.  It's certainly
less featureful.

For example, when dhclient does a renew, NetworkManager does not run any script
in /etc/NetworkManager/dispatcher.d/.  Those only seem to be run when
NetworkManager changes state on a device using either "up" or "down". 
NetworkManager's actions after the renew causes some other services to have to
rediscover the interface:

Jul 10 01:48:22 laptop dhclient: DHCPREQUEST on wlan0 to 192.168.1.1 port 67
Jul 10 01:48:22 laptop dhclient: DHCPACK from 192.168.1.1
Jul 10 01:48:22 laptop dhclient: bound to 192.168.1.6 -- renewal in 42559 
seconds.
Jul 10 01:48:22 laptop NetworkManager:   DHCP: device wlan0 state changed
bound -> renew
Jul 10 01:48:22 laptop NetworkManager: address 192.168.1.6
Jul 10 01:48:22 laptop NetworkManager: netmask 255.255.255.0
Jul 10 01:48:22 laptop NetworkManager: gateway 192.168.1.1
Jul 10 01:48:22 laptop NetworkManager: nameserver '127.0.0.1'
Jul 10 01:48:22 laptop avahi-daemon[2579]: Withdrawing address record for
192.168.1.6 on wlan0.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Leaving mDNS multicast group on
interface wlan0.IPv4 with address 192.168.1.6.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Interface wlan0.IPv4 no longer
relevant for mDNS.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Joining mDNS multicast group on
interface wlan0.IPv4 with address 192.168.1.6.
Jul 10 01:48:22 laptop avahi-daemon[2579]: New relevant interface wlan0.IPv4 for
mDNS.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Registering new address record for
192.168.1.6 on wlan0.IPv4.
Jul 10 01:48:23 laptop NetworkManager:   Policy set (wlan0) as default
device for routing and DNS.

I run openvpn as a service, outside of NetworkManager.  Using the normal
dhclient-script hooks, I can detect this action and restart the openvpn service
when it happens.  The /usr/libexec/nm-dhcp-client.action script NetworkManager
runs from dhclient doesn't appear to be able to handle the same idea of hooks. 
Without a cronjob watching things, or modifying NetworkManager's init script to
use the normal dhclient-script, I have to manually restart openvpn everytime
DHCP renews.  It tends to be less than transparent.

Should this replacement for dhclient-script read and handle the same hooks files
that dhclient-script itself uses, or should NetworkManager itself not make
changes to an interface like this when a simple renew happens?  Ideally,
functionality replaced should not be a reduction.  I'd like to see the hooks 
work.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/293139/comments/2

[Touch-packages] [Bug 308713] Re: vim-gnome freezing from any GTK event at Jaunty

[Bug Watch Updater]

Launchpad has imported 28 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=463908.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-09-25T10:12:29+00:00 Aioanei wrote:

Description of problem:

After starting gvim, either from commandline or from the menu, gnome, or
xfce, regardless, the window becomes unresponsive and the whole desktop
becomes unresponsive also. Only issuing 'killall gvim' or 'kill -9
' from a VT gives me back my desktop.

Version-Release number of selected component (if applicable):
7.2.13

How reproducible:
every time

Steps to Reproduce:
1.start gvim
2.
3.
  
Actual results:
The window and the desktop stop responding.

Expected results:
A useful gvim window

Additional info:
If it's indeed a gvim bug, since plain vim works great, from my little 
programming backround i'd say it's line 508 from src/gui.c 
[gui_create_initial_menus(root_menu)]; hope it's of any help.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/0


On 2008-09-29T10:25:11+00:00 Karsten wrote:

does gvim start with 'gvim -u NONE -U NONE' ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/1


On 2008-09-30T10:04:29+00:00 Karsten wrote:

Got requested info per mail:
It does start, but the problem persists, eg if i try to use its menus(file, 
edit, ehlp, etc), it locks up and it
locks my desktop too, and only a killall from a VT solves it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/2


On 2008-10-28T07:00:13+00:00 Joachim wrote:

Same problem here on an x86_64 system in sync with the "rawhide" tree.
After launching gvim, mouse input seems to be grabbed by gvim and only
gets released after doing a 'killall gvim' from a virtual console.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/3


On 2008-11-12T07:44:33+00:00 Joachim wrote:

Issue does not occur on an equivalent x86 system updated to F10 + updates from 
Koji. Whereas the x86_64 system from comment #3 is using an ATI Radeon X800 
video card, the x86 system is equipped with an Intel Corporation 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device
This bug is -really- annoying ..
Any suggestions how to investigate further into this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/4


On 2008-11-13T11:38:44+00:00 Joachim wrote:

After installing FC10-Snap3 x86_64 from scratch from the live CD after
updating several packages of the live system including anaconda, and
updating the installed system to current Koji immediately after the
first boot from run level 1, gvim behaves correctly. One of the updates
(which one?) did the job, so this issue should not be one anymore for
F10 final [plus updates].

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/5


On 2008-11-13T11:39:53+00:00 Joachim wrote:

Well, I meant to write "After installing F10-PR-x86_64 from scratch ..".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/6


On 2008-11-13T11:53:53+00:00 Karsten wrote:

Have you tried to reproduce this with a newly created user ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/7


On 2008-11-13T12:30:06+00:00 Joachim wrote:

Yes, but I had done either this or removed all dot directories also during the 
last weeks after installing each F10 snapshot and preview release respectively.
But only now, the focus problem is gone ..
As pointed out in comment #4, I hadn't observed this issue on a different x86 
system with the same Koji setup.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/8


On 2008-11-13T13:42:16+00:00 Karsten wrote:

There were no changes in vim which could have fixed this, I think it is save to 
assume that something in gtk/glib2 has caused this issue.
Does everyone agree that this bugzilla can be closed ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/9


On 

[Touch-packages] [Bug 410407] Re: Buttons don't respond to mouse clicks

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=542424.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-11-29T19:24:18+00:00 Hicham wrote:

Description of problem:
With compiz enabled flash objects become unresponsive.

Version-Release number of selected component (if applicable):
nspluginwrapper-1.3.0-8.fc12.i686

How reproducible:
always

Steps to Reproduce:
1.Enable compiz on F12
2.Open a webpage with flash objects
3.Try to click on them
  
Actual results:
no response to mouse clicks

Expected results:
response to mouse clicks

Additional info:
a temporary workaround would be to add the line
export GDK_NATIVE_WINDOWS=1 
to npviewer.sh

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/196


On 2009-12-01T05:02:40+00:00 Walter wrote:

Is this directly related to Adobe Reader not functioning?  At work we've
also discovered that Lotus Notes 8.5 has a "grey screen" which
unfortunately the GDK_NATIVE_WINDOWS workaround does not help with (it
doesn't make it to eclipse for whatever reason when executing the main
notes bin with the workaround env set, which is the GUI with the
problem) and the only workaround so far is to LD_PRELOAD 2.16 GTK libs.

Is a fix at the GTK level in the works, or is there a GTK bug at all?
I'm sure more of these things will be found, hopefully most of them
easily fixed with the GDK_NATIVE_WINDOWS workaround.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/198


On 2009-12-01T12:50:02+00:00 Hicham wrote:

No, it is not, and it is not Fedora specific, it is introduced by gtk
2.18. Official Adobe Flash are suffering from this bug, I don't know
about gnash. I think of it as a third party issue, since current Adobe
Flash Plugin have been released before gtk-2.18.

I was confused about where to file the bug, but since we can have a
temporary fix in Fedora, i preferred filing the bug here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/199


On 2009-12-04T13:15:55+00:00 Ben wrote:

A work around is described here:

http://forums.fedoraforum.org/showthread.php?t=233489

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/202


On 2009-12-04T13:22:48+00:00 Walter wrote:

Already documented in the F12 Common Bugs..
https://fedoraproject.org/wiki/Common_F12_bugs#Non_Responsive_Flash_Objects

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/203


On 2009-12-04T15:22:28+00:00 Martin wrote:

Added to nspluginwrapper-1.3.0-10.fc12

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/204


On 2009-12-04T15:34:03+00:00 Fedora wrote:

nspluginwrapper-1.3.0-10.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/nspluginwrapper-1.3.0-10.fc12

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/205


On 2009-12-04T18:02:34+00:00 Hicham wrote:

Thanks Martin for the fix ! can we close this bug report now ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/206


On 2009-12-07T07:32:29+00:00 Fedora wrote:

nspluginwrapper-1.3.0-10.fc12 has been pushed to the Fedora 12 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/207


** Changed in: nspluginwrapper (Fedora)
   Status: Unknown => Fix Released

** Changed in: nspluginwrapper (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/410407

Title:
  Buttons don't respond to mouse clicks

Status in Chromium Browser:
  Invalid
Status in Compiz:
  Invalid
Status in Mozilla Firefox:
  Invalid
Status in opera-browser:
  Invalid
Status in adobe-flashplugin package in Ubuntu:
  Invalid
Status in epiphany-browser 

[Touch-packages] [Bug 449401] Re: nm 0.8 lacks feature to unlock SIM by PUK

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=542319.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-11-29T09:51:33+00:00 Didier wrote:

Description of problem:

NetworkMananger configuration screen for large band connections does not
longer display field to specify PUK code for 3G modem

Version-Release number of selected component (if applicable):

NetworkManager-0.7.996-7.git20091113.fc12.rpm

How reproducible:

n/a

Steps to Reproduce:
1. n/a
2.
3.
  
Actual results:

NetworkMananger does not longer display field to specify PUK code for 3G
modem

Expected results:

NetworkManager should dispaly field to specify PUK code for 3G modem
when configuring large band connection

Additional info:

Log of a case where PUK is needed :

Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) starting 
connection 'SFR Par défaut 1'
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 3 -> 4 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) scheduled...
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) started...
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 4 -> 6 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) complete.
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) scheduled...
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) started...
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 6 -> 4 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) complete.
Nov 29 01:31:36 localhost modem-manager: (ttyUSB0) opening serial device...
Nov 29 01:31:36 localhost NetworkManager:   stage1_prepare_done(): GSM 
modem connection failed: SIM PUK required
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 4 -> 9 (reason 1)
Nov 29 01:31:36 localhost NetworkManager:   Marking connection 'SFR Par 
défaut 1' invalid.
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) failed.
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 9 -> 3 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): deactivating 
device (reason: 0).
Nov 29 01:31:36 localhost NetworkManager: flush_routes: assertion `iface_idx >= 
0' failed
Nov 29 01:31:36 localhost NetworkManager: flush_addresses: assertion `iface_idx 
>= 0' failed
Nov 29 01:31:36 localhost modem-manager: (ttyUSB0) closing serial device...

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/449401/comments/1


On 2009-12-21T11:46:15+00:00 Didier wrote:

My previous entry above is incomplete.

When I get message

<< NetworkManager:   stage1_prepare_done(): GSM modem connection
failed: SIM PUK required >>

the only solution with current version of NetworkManager is to boot on
Windows or to remove SIM from USB stick and insert it in mobile phone to
unlock it with the PUK code.

With previous versions of NetworkManager who accepted PUK code during
configuration, behavior was different and NetworkManager was able to
unlock the SIM so current behavior is a regression.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/449401/comments/3


On 2010-01-23T15:30:00+00:00 Johan wrote:

I just updated to Fedora-rawhide my kernel, ModemManager, NetworManager... but 
have the same problem.
I found another solution to unlock the sim, using wvdial to send:
AT+CPIN="puk","pin"

One thing to try may be to use the PIN field of the NetworkManager to send
puk,pin and not just the pin.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/449401/comments/4


On 2010-06-26T00:19:35+00:00 Dan wrote:

Recent versions of NM & ModemManager from updates will request the PUK
when the card is plugged in, if the card is locked enough to require the
PUK.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/449401/comments/5


** Changed in: network-manager (Fedora)
   Status: Confirmed => Fix Released

** Changed in: network-manager (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 461303] Re: generates-bad-code regression

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=544358.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-12-04T17:34:33+00:00 nucleo wrote:

Description of problem:
cryptest from cryptopp hangs up when built for fc13.
cryptest is running in %check section of cryptopp.spec, so cryptopp can't be 
built for fc13.
For fc12 cryptopp builds fine.


Version-Release number of selected component (if applicable):
binutils 2.20.51.0.2-8.fc13


See the same issues here:

http://sourceware.org/bugzilla/show_bug.cgi?id=10856

https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/32


On 2009-12-09T12:09:27+00:00 Nick wrote:

Hi Alec,

  I have imported Alan Modra's patch for PR 10856 into the devel
binutils rpm.  Please try using the latest release (2.20.51.0.2-9), and
if you still have problems, let us know.

Cheers
  Nick

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/33


On 2009-12-09T15:06:21+00:00 nucleo wrote:

Hi Nick,

With binutils 2.20.51.0.2-9.fc13 cryptopp test not fails.

Finally cryptopp-5.6.1-0.1.svn479.fc13 built:
http://koji.fedoraproject.org/koji/buildinfo?buildID=143094

Should I close this bug?

Alexey

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/34


On 2009-12-13T21:03:18+00:00 Zooko wrote:

This page on launchpad is tracking the progress of this issue through
several different operating systems and open source projects that are
affected by this bug.  I added a link to this ticket on
bugzilla.redhat.com:

https://bugs.launchpad.net/fedora/+source/binutils/+bug/461303

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/37


On 2010-04-21T16:53:22+00:00 Michal wrote:

Notes: Changing version to 13 from 12, since wrt comment 0 it is clear
that F-13 had that issue not F-12. Closing, we have update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/39


On 2012-01-11T19:58:39+00:00 Zooko wrote:

If anybody reading this has the authority to change the status of
tickets in launchpad, please mark this as fixed there:
https://bugs.launchpad.net/fedora/+source/binutils/+bug/461303 . Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/45


** Changed in: binutils (Fedora)
   Status: In Progress => Fix Released

** Changed in: binutils (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/461303

Title:
  generates-bad-code regression

Status in binutils:
  Fix Released
Status in MinGW:
  Unknown
Status in pycryptopp:
  Fix Released
Status in Tahoe-LAFS:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in libcrypto++ package in Ubuntu:
  Invalid
Status in binutils source package in Karmic:
  Fix Released
Status in libcrypto++ source package in Karmic:
  Invalid
Status in binutils package in Fedora:
  Fix Released

Bug description:
  g++-4.4 4.4.1-3ubuntu3 was used to build libcrypto++8.  The current
  g++-4.4 in Karmic is g++-4.4 4.4.1-4ubuntu8.  When 4.4.1-4ubuntu8 is
  used to build libcrypto++8 then the libcrypto++8 self-tests hang
  during the SHA validation.  It appears that there has been a
  regression between g++ 4.4.1-3ubuntu3 and -4ubuntu8 such that the new
  one generates bad code.

  In addition to the libcrypto++8 self-tests hanging during SHA
  validation, if you then build python-pycryptopp using the libcrypto++8
  lib that was built by g++ 4.4.1-4ubuntu8, then the python-pycryptopp
  library gets segfaults when it runs its self-tests. Here is the
  pycryptopp upstream buildbot showing segfaults on karmic, along with a
  valgrind report:

  http://allmydata.org/buildbot-pycryptopp/waterfall
  
http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk/builds/11/steps/test/logs/valgrind

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/461303/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1375555] Re: global static TLS slot limit breaks the x86 emulator

[Bug Watch Updater]

Launchpad has imported 35 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1124987.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-07-30T19:22:15+00:00 Adam wrote:

Description of problem:
Crashes on startup in current F21.

Version-Release number of selected component:
calibre-1.46.0-1.fc21

Additional info:
reporter:   libreport-2.2.3
cmdline:python2 /usr/bin/calibre --detach
executable: /usr/bin/calibre
kernel: 3.16.0-0.rc6.git2.2.fc22.x86_64
runlevel:   N 5
type:   Python
uid:1001

Truncated backtrace:
#1  in /usr/lib64/calibre/calibre/utils/magick/__init__.py:14
#2  in /usr/lib64/calibre/calibre/db/backend.py:31
#3  in /usr/lib64/calibre/calibre/db/legacy.py:17
#4  in /usr/lib64/calibre/calibre/gui2/ui.py:26
#5 run_gui in /usr/lib64/calibre/calibre/gui2/main.py:320
#6 main in /usr/lib64/calibre/calibre/gui2/main.py:458
#7  in /usr/bin/calibre:20

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/0


On 2014-07-30T19:22:18+00:00 Adam wrote:

Created attachment 922690
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/1


On 2014-07-30T19:22:19+00:00 Adam wrote:

Created attachment 922691
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/2


On 2014-08-06T13:17:25+00:00 Colin wrote:

I suspect this is a glibc change.  We're seeing the same error message
in an Anaconda environment from trying to dlopen(libgtk.so).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/3


On 2014-08-06T13:20:12+00:00 Adam wrote:

So, let's CC the glibc maintainer (at least, the person to whom glibc
bugs appear currently to be assigned).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/4


On 2014-08-08T12:41:54+00:00 Adam wrote:

Created attachment 925164
LD_DEBUG log from crash (requested by carlos)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/5


On 2014-08-08T12:51:31+00:00 Carlos wrote:

Please get the list of all shared libraries loaded by python then run
`readelf -a -W` against all of them and dump that to a file. I want to
know which if the libraries is using static TLS.

The error you are seeing is not a bug in glibc. The dynamic loader has a
fixed amount of "super fast" static TLS for use by core libraries which
are always loaded and can use this static TLS. Normal libraries should
not be using static TLS and you should not be running out of static TLS,
those loaded libraries should be using dynamic TLS which has no limits
(not quite as fast as static TLS but still fast).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/6


On 2014-08-08T13:30:38+00:00 Colin wrote:

This is a good post on the issue:

http://stackoverflow.com/questions/19268293/matlab-error-cannot-open-
with-static-tls

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/7


On 2014-08-08T13:32:52+00:00 Kevin wrote:

"Please get the list of all shared libraries loaded by python then run
`readelf -a -W` against all of them and dump that to a file."

Is there some easy way to get this list without parsing the strace
output?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/8


On 2014-08-08T19:26:34+00:00 Adam wrote:

I thought it might be in the abrt data, but I don't see it in there at
least in an obvious way. I can do the parsing, I just didn't want to
embarrass myself doing it in my monkey way in front of carlos :P when I
have some privacy to pore over the 'cut' manpages without anyone seeing,
I'll get it done...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/9


On 2014-08-09T07:20:38+00:00 Carlos wrote:

(In reply to Adam Williamson (Red Hat) from comment #9)
> I thought it might be in the abrt data, but I don't see it in there at least
> in an obvious way. I can do the 

[Touch-packages] [Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

[Bug Watch Updater]

** Changed in: pulseaudio (Fedora)
   Status: Unknown => Won't Fix

** Changed in: pulseaudio (Fedora)
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1710060

Title:
  Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio package in Fedora:
  Won't Fix

Bug description:
  Whenever I choose the Jabra Evolve 65 UC Headset as the playback
  device, there are sound chipmunks. The same was the case with Jabra
  Motion Headset as well. But those two headsets worked perfectly in
  Windows, Mac OS and Android.

  There was a workaround mentioned in
  https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the
  contents of /etc/pulseaudio/daemon.conf :

  Changing

   ;default-sample-rate=44100

  to

   default-sample-rate=48000

  and then running

   pulseaudio -k

  made the sound on Jabra good (no more chipmunks). Also, when I opened
  the Sound Settings with the changes in daemon.conf in place, there
  seems to be some distortions in headset sound, which goes away few
  seconds after I close the sound settings window.

  This problem should be fixed, as many new Linux users will find it
  difficult to edit files requiring root access, and those who do not
  use command line won't be okay with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   itachi10880 F...m pulseaudio
   /dev/snd/controlC2:  itachi10880 F pulseaudio
   /dev/snd/controlC1:  itachi10880 F pulseaudio
   /dev/snd/controlC0:  itachi10880 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 10 21:11:18 2017
  InstallationDate: Installed on 2016-08-27 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727918] Re: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1727918

Title:
  package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Happened while installing gparted

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   libgtkmm-2.4-1v5:amd64: Install
   libparted-fs-resize0:amd64: Install
   gparted:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports: 600:0:122:252397:2017-10-26 21:36:05.151989698 -0600:2017-10-26 
21:36:06.151989698 -0600:/var/crash/python3-apport.0.crash
  Date: Thu Oct 26 21:36:05 2017
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4.5
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-10-27 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-10-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1727918/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727918] [NEW] package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[agahowa23]

Public bug reported:

Happened while installing gparted

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-apport 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 libgtkmm-2.4-1v5:amd64: Install
 libparted-fs-resize0:amd64: Install
 gparted:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CrashReports: 600:0:122:252397:2017-10-26 21:36:05.151989698 -0600:2017-10-26 
21:36:06.151989698 -0600:/var/crash/python3-apport.0.crash
Date: Thu Oct 26 21:36:05 2017
DuplicateSignature:
 package:python3-apport:2.20.4-0ubuntu4.5
 Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
 dpkg: error processing package python3-apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-10-27 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: apport
Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to zesty on 2017-10-27 (0 days ago)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1727918

Title:
  package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Happened while installing gparted

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   libgtkmm-2.4-1v5:amd64: Install
   libparted-fs-resize0:amd64: Install
   gparted:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports: 600:0:122:252397:2017-10-26 21:36:05.151989698 -0600:2017-10-26 
21:36:06.151989698 -0600:/var/crash/python3-apport.0.crash
  Date: Thu Oct 26 21:36:05 2017
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4.5
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-10-27 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-10-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1727918/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727039] Re: Xorg crash

[Daniel C Aragao]

** Package changed: xorg (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1727039

Title:
  Xorg crash

Status in Ubuntu:
  New

Bug description:
  I got some messages in logs program.

  Message:
  "CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar 
StartServiceByName para org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1"

  
  Message: 
  "Unrecoverable failure in required component org.gnome.Shell.desktop"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 24 16:32:43 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 370E4K
  dmi.product.version: P06RCX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1727039/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727770] Re: wayland does not have logic for a Lenovo laptop on the dock

[Daniel van Vugt]

** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu)

** Summary changed:

- wayland does not have logic for a Lenovo laptop on the dock
+ If I resume on the dock, Gnome Shell seems to recognize the lid as closed and 
suspends

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1727770

Title:
  If I resume on the dock, Gnome Shell seems to recognize the lid as
  closed and suspends

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a Lenovo T440s (haswell) and an ultradock with external
  monitor.

  If I resume on the dock, wayland seems to recognize the lid as closed
  and suspends. The work around is to (1) open the lid, bring up the
  display control tab and switch to single monitor, choose the external
  one (on the DP); and (3) apply.  Then I can close the lid.

  The laptop will boot correctly on the dock with the lid closed.

  I tried changing the dconf parameter org.gnome.settings-
  daemon.plugins.power to 'nothing' but that doesn't seem to matter.

  Obviously, this is not a critical issue, but it sure is annoying.
  This should "just work".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-server0 1.14.0-1
  Uname: Linux 4.13.9-041309-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:59:35 2017
  Dependencies:
   gcc-7-base 7.2.0-8ubuntu3
   libc6 2.26-0ubuntu2
   libffi6 3.2.1-6
   libgcc1 1:7.2.0-8ubuntu3
  DistUpgraded: 2017-10-20 11:39:46,873 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.13.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 4.13.9-041309-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2016-05-06 (537 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.9-041309-generic 
root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727770/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727867] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from _int_realloc() from __GI___libc_realloc() from g_realloc() from g_string_maybe_expand

[Daniel van Vugt]

** Summary changed:

- bluetoothd crashed with SIGSEGV in malloc_consolidate()
+ bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() 
from _int_realloc() from __GI___libc_realloc() from g_realloc() from 
g_string_maybe_expand() from g_string_append_vprintf()

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727867

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate() from
  _int_malloc() from _int_realloc() from __GI___libc_realloc() from
  g_realloc() from g_string_maybe_expand() from
  g_string_append_vprintf()

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0

  ---

  While trying to pair with a mouse (microsoft sculpt mouse)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 26 23:42:52 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-06-22 (125 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FBCTO1WW
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/vg--hostname-root--ubuntu ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f6907f6d108 :   mov
0x8(%rbx),%rax
   PC (0x7f6907f6d108) ok
   source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489
   _int_malloc (av=av@entry=0x7f69082bec20 , 
bytes=bytes@entry=1025) at malloc.c:3705
   _int_realloc (av=av@entry=0x7f69082bec20 , 
oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at 
malloc.c:4626
   __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245
   g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to artful on 2017-10-09 (17 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: E4:A4:71:4F:31:79  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN
    RX bytes:980135 acl:0 sco:0 events:12127 errors:0
    TX bytes:605335 acl:0 sco:0 commands:2477 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727867] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from _int_realloc() from __GI___libc_realloc() from g_realloc() from g_string_maybe_expand

[Daniel van Vugt]

Confirmed by:
https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0

** Description changed:

+ https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0
+ 
+ ---
+ 
  While trying to pair with a mouse (microsoft sculpt mouse)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 26 23:42:52 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-06-22 (125 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FBCTO1WW
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
-  LANG=fr_FR.UTF-8
-  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/vg--hostname-root--ubuntu ro quiet splash vt.handoff=7
  SegvAnalysis:
-  Segfault happened at: 0x7f6907f6d108 :   mov
0x8(%rbx),%rax
-  PC (0x7f6907f6d108) ok
-  source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f6907f6d108 :   mov
0x8(%rbx),%rax
+  PC (0x7f6907f6d108) ok
+  source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
-  malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489
-  _int_malloc (av=av@entry=0x7f69082bec20 , 
bytes=bytes@entry=1025) at malloc.c:3705
-  _int_realloc (av=av@entry=0x7f69082bec20 , 
oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at 
malloc.c:4626
-  __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245
-  g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489
+  _int_malloc (av=av@entry=0x7f69082bec20 , 
bytes=bytes@entry=1025) at malloc.c:3705
+  _int_realloc (av=av@entry=0x7f69082bec20 , 
oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at 
malloc.c:4626
+  __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245
+  g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to artful on 2017-10-09 (17 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: E4:A4:71:4F:31:79  ACL MTU: 1021:4  SCO MTU: 96:6
-   UP RUNNING PSCAN ISCAN 
-   RX bytes:980135 acl:0 sco:0 events:12127 errors:0
-   TX bytes:605335 acl:0 sco:0 commands:2477 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: E4:A4:71:4F:31:79  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN
+   RX bytes:980135 acl:0 sco:0 events:12127 errors:0
+   TX bytes:605335 acl:0 sco:0 commands:2477 errors:0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727867

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate() from
  _int_malloc() from _int_realloc() from __GI___libc_realloc() from
  g_realloc() from g_string_maybe_expand() from
  g_string_append_vprintf()

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0

  ---

  While trying to pair with a mouse (microsoft sculpt mouse)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 26 23:42:52 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-06-22 (125 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  

[Touch-packages] [Bug 1690013] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk

[Daniel van Vugt]

See also bug 1727914

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1690013

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate() from
  _int_malloc() from __libc_calloc() from __GI___open_memstream() from
  __GI___vsyslog_chk

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.41-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/c3d5226fc780ef2d3f4fcdf956712dafacd0be74 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727867] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from _int_realloc() from __GI___libc_realloc() from g_realloc() from g_string_maybe_expand

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727867

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate() from
  _int_malloc() from _int_realloc() from __GI___libc_realloc() from
  g_realloc() from g_string_maybe_expand() from
  g_string_append_vprintf()

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0

  ---

  While trying to pair with a mouse (microsoft sculpt mouse)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 26 23:42:52 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-06-22 (125 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FBCTO1WW
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/vg--hostname-root--ubuntu ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f6907f6d108 :   mov
0x8(%rbx),%rax
   PC (0x7f6907f6d108) ok
   source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489
   _int_malloc (av=av@entry=0x7f69082bec20 , 
bytes=bytes@entry=1025) at malloc.c:3705
   _int_realloc (av=av@entry=0x7f69082bec20 , 
oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at 
malloc.c:4626
   __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245
   g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to artful on 2017-10-09 (17 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: E4:A4:71:4F:31:79  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN
    RX bytes:980135 acl:0 sco:0 events:12127 errors:0
    TX bytes:605335 acl:0 sco:0 commands:2477 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727915] Re: /usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:g_realloc

[Daniel van Vugt]

*** This bug is a duplicate of bug 1727867 ***
https://bugs.launchpad.net/bugs/1727867

** This bug has been marked a duplicate of bug 1727867
   bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() 
from _int_realloc() from __GI___libc_realloc() from g_realloc() from 
g_string_maybe_expand() from g_string_append_vprintf()

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727915

Title:
  
/usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:g_realloc

Status in bluez package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.46-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727914] Re: bluetoothd crashed with SIGEMT in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk

[Daniel van Vugt]

See also bug 1690013

** Summary changed:

- 
/usr/lib/bluetooth/bluetoothd:7:malloc_consolidate:_int_malloc:__libc_calloc:__GI___open_memstream:__GI___vsyslog_chk
+ bluetoothd crashed with SIGEMT in malloc_consolidate() from _int_malloc() 
from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727914

Title:
  bluetoothd crashed with SIGEMT in malloc_consolidate() from
  _int_malloc() from __libc_calloc() from __GI___open_memstream() from
  __GI___vsyslog_chk

Status in bluez package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 
5.43-0ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/98da419ed3c25ad6b4e2fe408d176d1abed4d08c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727914/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727914] [NEW] bluetoothd crashed with SIGEMT in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 
5.43-0ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/98da419ed3c25ad6b4e2fe408d176d1abed4d08c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727914

Title:
  bluetoothd crashed with SIGEMT in malloc_consolidate() from
  _int_malloc() from __libc_calloc() from __GI___open_memstream() from
  __GI___vsyslog_chk

Status in bluez package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 
5.43-0ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/98da419ed3c25ad6b4e2fe408d176d1abed4d08c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727914/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727915] [NEW] /usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:g_realloc

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1727867 ***
https://bugs.launchpad.net/bugs/1727867

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.46-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful wily xenial yakkety zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1727915

Title:
  
/usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:g_realloc

Status in bluez package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.46-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727911] [NEW] fcitx not dispaly

[宋航]

Public bug reported:

Choice Fcitx
No Fcitx`sign on the top right corner

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 11:07:49 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
InstallationDate: Installed on 2017-10-24 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 4180AP3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET73WW (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4180AP3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T420
dmi.product.name: 4180AP3
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1727911

Title:
  fcitx not dispaly

Status in xorg package in Ubuntu:
  New

Bug description:
  Choice Fcitx
  No Fcitx`sign on the top right corner

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 11:07:49 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
  InstallationDate: Installed on 2017-10-24 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 4180AP3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180AP3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 4180AP3
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 329881] Re: Weather applet uses defunct station for Berlin weather

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=470099.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-11-05T18:53:12+00:00 Lebenskuenstler wrote:

I hope I report against the right package. If not so, please reassign.

Description of problem:

I am using the weather forecast feature at the GNOME Desktop. Since the
airport Berlin Tempelhof was closed at Oct 31rd it does not send correct
weather data anymore. Since this date, I at always has says something
about a weather of 4 degrees. Luckily it is currently not that cold
around here :)

If I use instead of Berlin Tempelhof Schönefeld or Tegel instead, I get
the correct weather data.

Version-Release number of selected component (if applicable):

Gnome 2.22, also Gnome 2.24

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/0


On 2008-11-26T04:50:00+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 10 
development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/1


On 2009-01-10T13:46:59+00:00 Steve wrote:

Confirming this bug with:
gnome-panel-2.24.2-1.fc10.i386
libgweather-2.24.2-1.fc10.i386

A Wireshark capture shows that the applet sends this query for Berlin-
Tempelhof:

http://weather.noaa.gov/cgi-bin/mgetmetar.pl?=EDDI

The reply includes this date/time: 2008/10/30 23:50 UTC

The panel applet could display this date/time so that a user would know
how old the observations are. It might also be useful to flag stale
observations (older than 24 hours, say).

Another enhancement would be to display the full location name.
For example, the "Current Conditions" tab could show "Berlin-Tempelhof" instead 
of  "Berlin".

Also, the label "City" is misleading. It would more accurate to say
"Location".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/2


On 2009-01-10T13:49:39+00:00 Steve wrote:

For completeness, here is the full reply from:
http://weather.noaa.gov/cgi-bin/mgetmetar.pl?=EDDI

Latest METAR Observation(s) for: EDDI
EDDI

The most recent METAR observation from EDDI in our system was generated
at the source at:

2008/10/30 23:50 UTC

The observation is:
EDDI 302350Z 26007KT  FEW006 BKN011 04/04 Q1003

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/3


On 2009-01-10T19:04:07+00:00 Steve wrote:

It appears that inactive stations are removed with the aid of a Python script.
http://svn.gnome.org/viewvc/libgweather/trunk/data/sources/README.sources?view=markup

However, Berlin-Tempelhof is in SVN rev. 534.
http://svn.gnome.org/viewvc/libgweather/trunk/data/Locations.xml.in?view=log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/4


On 2009-01-10T22:07:50+00:00 Steve wrote:

(In reply to comment #2)

> The panel applet could display this date/time so that a user would know how 
> old
> the observations are. It might also be useful to flag stale observations 
> (older
> than 24 hours, say).

See Bug 479539 -  Weather Report applet may report incorrect month for
"Last update"

> Another enhancement would be to display the full location name.
> For example, the "Current Conditions" tab could show "Berlin-Tempelhof" 
> instead
> of  "Berlin".

See Bug 479529 -  Weather Report applet does not display enough of the
location name

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/5


On 2009-01-13T14:52:33+00:00 Dan wrote:

re-filed upstream as http://bugzilla.gnome.org/show_bug.cgi?id=567607.
This will likely be fixed for F11.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/6


** Changed in: libgweather (Fedora)
   Status: Fix Released => Won't Fix

** Changed in: libgweather (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/329881

Title:
  Weather applet uses defunct station for Berlin weather

Status in 

[Touch-packages] [Bug 374397] Re: console-kit-daemon: glibgobject warning value location for gachararray passed as null

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=496636.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-04-20T13:33:37+00:00 Jonathan wrote:

With current Rawhide, I get four copies of this syslog message every
time I log in:

Apr 20 07:12:59 jik2 console-kit-daemon[2079]: GLib-GObject-WARNING: 
IA__g_object_get_valist: value location for `gchararray' passed as NULL
Apr 20 07:12:59 jik2 console-kit-daemon[2079]: GLib-GObject-WARNING: 
IA__g_object_get_valist: value location for `gchararray' passed as NULL
Apr 20 07:12:59 jik2 console-kit-daemon[2079]: GLib-GObject-WARNING: 
IA__g_object_get_valist: value location for `gchararray' passed as NULL
Apr 20 07:12:59 jik2 console-kit-daemon[2079]: GLib-GObject-WARNING: 
IA__g_object_get_valist: value location for `gchararray' passed as NULL

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/374397/comments/0


On 2009-04-21T03:58:53+00:00 Matthias wrote:

This might fix it, I think

diff -up ConsoleKit-0.3.0/src/ck-manager.c.null-warning 
ConsoleKit-0.3.0/src/ck-manager.c
--- ConsoleKit-0.3.0/src/ck-manager.c.null-warning  2009-04-20 
23:55:53.248884043 -0400
+++ ConsoleKit-0.3.0/src/ck-manager.c   2009-04-20 23:56:27.736126951 -0400
@@ -1213,7 +1213,7 @@ session_is_real_user (CkSession *session
 
 g_object_get (session,
   "unix-user", ,
-  "session-type", session_type,
+  "session-type", _type,
   NULL);
 
 username = get_user_name (uid);

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/374397/comments/2


On 2009-04-21T05:02:14+00:00 Matthias wrote:

Built in ConsoleKit-0.3.0-8.fc11

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/374397/comments/3


On 2009-06-09T14:12:42+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 11 
development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/374397/comments/11


** Changed in: consolekit (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to consolekit in Ubuntu.
https://bugs.launchpad.net/bugs/374397

Title:
  console-kit-daemon: glibgobject warning value location for gachararray
  passed as null

Status in ConsoleKit:
  Fix Released
Status in consolekit package in Ubuntu:
  Fix Released
Status in consolekit package in Fedora:
  Fix Released

Bug description:
  I use ubuntu jaunty 64 finale release
  When I shut down the system (the normal way) a pop-up window with a warning I 
don't have the time to read appears at the bottom of the desktop just before 
the system shuts down. I thought it was because I stop it before countdown is 
over but the same thing happens if I wait 'till the countdown is over. 
  So I opened the system reports to see what was written at the time of this 
pop-up warning and all I found was this : 

   noun-desktop console-kit-daemon[2805]: GLib-GObject-WARNING: 
IA__g_object_get_valist: value location for `gchararray' passed as NULL 
  May 10 00:37:13 noun-desktop last message repeated 6 times
  May 10 00:37:13 noun-desktop init: tty4 main process (2500) killed by TERM 
signal
  May 10 00:37:13 noun-desktop init: tty5 main process (2501) killed by TERM 
signal
  May 10 00:37:13 noun-desktop init: tty2 main process (2508) killed by TERM 
signal
  May 10 00:37:13 noun-desktop init: tty3 main process (2509) killed by TERM 
signal
  May 10 00:37:13 noun-desktop init: tty6 main process (2510) killed by TERM 
signal
  May 10 00:37:13 noun-desktop init: tty1 main process (3350) killed by TERM 
signal
  May 10 00:37:13 noun-desktop console-kit-daemon[2805]: GLib-GObject-WARNING: 
IA__g_object_get_valist: value location for `gchararray' passed as NULL 
  May 10 00:37:13 noun-desktop last message repeated 5 times
  May 10 00:37:16 noun-desktop bluetoothd[2967]: bridge pan0 removed
  May 10 00:37:16 noun-desktop bluetoothd[2967]: Stopping SDP server
  May 10 00:37:16 noun-desktop bluetoothd[2967]: Exit

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/yelp
  NonfreeKernelModules: nvidia
  Package: yelp 2.25.1-0ubuntu5
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  

[Touch-packages] [Bug 506798] Re: du crashes when traversing nfs mounted .snapshot directories

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=533569.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-11-07T11:52:48+00:00 Jim wrote:

Description of problem: in the vicinity of a mount point directory, two
directories may have the same device and inode number.  This is a
serious problem because many tools treat the condition as indicating a
hard directory cycle, which usually indicates file system corruption.

Version-Release number of selected component (if applicable):
2.6.31.5-122.fc12.x86_64

How reproducible: every time

Steps to Reproduce:
Based on the set-up from Kamil Dudka in 
https://bugzilla.redhat.com/show_bug.cgi?id=501848#c45

# mount | grep ^/
...
/dev/sda8 on /home type ext4 (rw,noatime)
...
# top=/home
# cat /etc/exports
# printf "/ *(fsid=0,crossmnt)\n$top *(crossmnt)\n" >> /etc/exports
# service nfs restart
...
# mkdir /tmp/mnt
# mount -t nfs4 localhost:/ /tmp/mnt
# stat --printf "%d %i %n\n" /tmp/mnt{,$top}
22 2 /tmp/mnt
22 2 /tmp/mnt/home

Then, using the very latest du from upstream coreutils.git,
I see this:

$ du /tmp/mnt > /dev/null
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
  `/tmp/mnt/home'

Actual results: above


Expected results: different dev and/or inode, no du failure


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/0


On 2009-11-10T18:33:05+00:00 Steve wrote:

> # stat --printf "%d %i %n\n" /tmp/mnt{,$top}
> 22 2 /tmp/mnt
> 22 2 /tmp/mnt/home
I do see this... but 

> $ du /tmp/mnt > /dev/null
> du: WARNING: Circular directory structure.
> This almost certainly means that you have a corrupted file system.
> NOTIFY YOUR SYSTEM MANAGER.
> The following directory is part of the cycle:
> `/tmp/mnt/home'

What kernel are you using and nfs-utils

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/1


On 2009-11-10T18:35:03+00:00 Steve wrote:

I meant to say... I don't see the du error... what kernel/nfs-utils are
you using..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/2


On 2009-11-10T18:37:09+00:00 Kamil wrote:

(In reply to comment #2)
> I meant to say... I don't see the du error... what kernel/nfs-utils are
> you using..  

You need to compile GNU coreutils from git to see the error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/3


On 2009-11-10T18:39:56+00:00 Jim wrote:

Hi Steve, kernel version is listed above.
nfs-utils-1.2.0-18.fc12.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/4


On 2009-11-10T18:45:33+00:00 Jeff wrote:

I think I understand what the issue is here. I just don't think that
there's much we can do about it...

The stat program is doing a lstat() and that doesn't trigger a submount
(LOOKUP_FOLLOW isn't set). So we end up doing a GETATTR call that
returns info on the root inode of the /home mount. So the stat() syscall
gets the "real" st_ino of /tmp/mnt/home, but the st_dev is still that of
the parent (/tmp/mnt).

This is particularly evident here because the root of any ext3/4
filesystem has an st_ino of 2.

I think our options are:

1) fix the kernel to trigger a submount even when LOOKUP_FOLLOW isn't
set (quite possibly very hard on performance)

2) fix the kernel to return a bit more info when we have a "potential
mountpoint" like this. My suggestion on LKML was to coopt a new
st_mode/i_mode bit and use that to indicate that a directory is
potentially a new mountpoint if someone were to walk into it

So far, my suggestion hasn't received any feedback upstream.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/5


On 2009-11-16T15:17:01+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 12 
development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/506798/comments/6

[Touch-packages] [Bug 489398] Re: Unable to use use LVM with DRBD block devices as PV

[Bug Watch Updater]

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=530881.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-10-25T19:59:22+00:00 Wolfgang wrote:

Description of problem:

I'm trying to set up a nested LVM configuration with DRBD, see for example
http://www.drbd.org/users-guide-emb/s-nested-lvm.html . Creating logical 
volumes on top of a DRBD device fails.

Version-Release number of selected component (if applicable):

lvm2-2.02.48-2.fc11.i586
kernel-2.6.30.8-64.fc11.i586

How reproducible:

stable, happens always.

Steps to Reproduce:
1. set up a DRBD device
2. create a physical volume on it:
# pvcreate /dev/drbd0
  Physical volume "/dev/drbd0" successfully created
3. create a volume group on it:
# vgcreate replicated /dev/drbd0
  Volume group "replicated" successfully created
# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "replicated" using metadata type lvm2
  Found volume group "vg0" using metadata type lvm2
  Found volume group "vg1" using metadata type lvm2
# vgchange -a y replicated
  0 logical volume(s) in volume group "replicated" now active
4. try to create a logical volum:
# lvcreate --name foo --size 32G replicated
  device-mapper: reload ioctl failed: Invalid argument
  Aborting. Failed to activate new LV to wipe the start of it.

Actual results:

LV not created.

Error messages on stdout:
  device-mapper: reload ioctl failed: Invalid argument
  Aborting. Failed to activate new LV to wipe the start of it.
Syslog messages:
# Oct 24 21:44:01 gemini kernel: device-mapper: table: 253:11: linear: 
dm-linear: Device lookup failed
Oct 24 21:44:01 gemini kernel: device-mapper: ioctl: error adding target to 
table

Expected results:

LV created, no error messages.

Additional info:

I am pretty sure that used to work in older versions (probably F9 or F10),
but unfortunately I don't have any records of this setup any more.

There are similar bug reports from other distributions, so this seems to
be a generic (kernel?) issue, see for example http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=533436

Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/0


On 2009-10-25T20:23:22+00:00 Alasdair wrote:

As per the Debian bug, run the tool with -, look for the line similar to 
this one:
   Adding target: 0 8388608 linear 252:2 384

Take the '252:2' there as major:minor and investigate the state of that
device.  Report all its attributes - use 'blockdev', find it in
/sys/block etc.  Check if anything has it open.  Check its size etc.
etc.

Also test with udev disabled in case that's interfering.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/1


On 2009-10-26T14:03:42+00:00 Wolfgang wrote:

Created attachment 366101
Running pvcreate, vgcreate and lvcreate with "-" + additional info

Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/2


On 2009-10-26T14:04:37+00:00 Wolfgang wrote:

OK, I attached the requested additional information - the only thing I
cannot do right now is testing without udev - I don't know how to
disable udev (and still have a resonably "normal" Fedora 11 running).
Please advice if really needed - although I don't see where udev
would interfere.

[Note this is from another system, actually the peer; problem is the
very same though.]

Please let me know if any additional information is requqired.

Wolfgang Denk, w...@denx.de

Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/3


On 2009-10-26T14:14:52+00:00 Milan wrote:

Please can you also attach output (tarball) from lvmdump?
(from some system where is /dev/drbd* device present and lvm fails)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/4


On 2009-10-26T14:25:01+00:00 Wolfgang wrote:

Created attachment 366106
Output of "lvmdump -a -m"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/5


On 2009-10-26T14:51:12+00:00 Milan wrote:

Thanks.

There is something strange:
- you create pvcreate /dev/drbd0 (/dev/drbd0 is major:minor 147:0)
- but in metadata PV as /dev/dm-2 (which is 253:2 and in fact it is vg0/drbd0 
volume mapped to 8:3 - which is /dev/sda3)

So now we need to find where 

[Touch-packages] [Bug 1167994] Re: [12d1:1506] Huawei E398 LTE/UMTS/GSM modem does not work

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1014341.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-10-01T18:50:30+00:00 Mikhail wrote:

Demonstration:
https://docs.google.com/file/d/0B0nwzlfiB4aQOTM5dk5ZeDJQdHc/edit?usp=sharing

dmesg
[ 8153.859898] usb 2-3: new high-speed USB device number 5 using ehci-pci
[ 8153.975377] usb 2-3: New USB device found, idVendor=12d1, idProduct=14fe
[ 8153.975387] usb 2-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 8153.975391] usb 2-3: Product: HUAWEI Mobile
[ 8153.975395] usb 2-3: Manufacturer: HUAWEI Technology
[ 8154.021700] usb-storage 2-3:1.0: USB Mass Storage device detected
[ 8154.022707] scsi8 : usb-storage 2-3:1.0
[ 8154.023037] usb-storage 2-3:1.1: USB Mass Storage device detected
[ 8154.025153] scsi9 : usb-storage 2-3:1.1
[ 8154.673213] usb 2-3: USB disconnect, device number 5
[ 8155.026168] usb 2-3: new high-speed USB device number 6 using ehci-pci
[ 8155.141593] usb 2-3: New USB device found, idVendor=12d1, idProduct=1506
[ 8155.141607] usb 2-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 8155.141615] usb 2-3: Product: HUAWEI Mobile
[ 8155.141622] usb 2-3: Manufacturer: HUAWEI Technology
[ 8155.145379] option 2-3:1.0: GSM modem (1-port) converter detected
[ 8155.146691] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0
[ 8155.150118] usb 2-3: MAC-Address: 0c:5b:8f:27:9a:64
[ 8155.151164] cdc_ncm 2-3:1.1 wwan0: register 'cdc_ncm' at usb-:00:13.2-3, 
Mobile Broadband Network Device, 0c:5b:8f:27:9a:64
[ 8155.152316] usb-storage 2-3:1.2: USB Mass Storage device detected
[ 8155.156235] scsi10 : usb-storage 2-3:1.2
[ 8155.156563] usb-storage 2-3:1.3: USB Mass Storage device detected
[ 8155.159099] scsi11 : usb-storage 2-3:1.3
[ 8155.260584] systemd-udevd[4129]: renamed network interface wwan0 to 
wwp0s19f2u3i1
[ 8156.159144] scsi 10:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
[ 8156.164484] sr0: scsi-1 drive
[ 8156.165365] sr 10:0:0:0: Attached scsi CD-ROM sr0
[ 8156.166454] sr 10:0:0:0: Attached scsi generic sg1 type 5
[ 8156.167388] scsi 11:0:0:0: Direct-Access HUAWEI   TF CARD Storage  2.31 
PQ: 0 ANSI: 2
[ 8156.168833] sd 11:0:0:0: Attached scsi generic sg2 type 0
[ 8156.170970] sd 11:0:0:0: [sdb] Attached SCSI removable disk
[ 8156.524613] ISO 9660 Extensions: Microsoft Joliet Level 1
[ 8156.525147] ISOFS: changing to secondary root
[ 8156.525774] SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts

[mikhail@localhost ~]$ lsusb
Bus 002 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 
LTE/UMTS/GSM Modem/Networkcard
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04f2:b1d8 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[mikhail@localhost ~]$ ifconfig
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 0  (Local Loopback)
RX packets 1014  bytes 84012 (82.0 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1014  bytes 84012 (82.0 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p4p1: flags=4099  mtu 1500
ether c8:0a:a9:95:84:65  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163  mtu 1500
inet 192.168.1.186  netmask 255.255.255.0  broadcast 0.0.0.0
inet6 fe80::7ae4:ff:feab:2a86  prefixlen 64  scopeid 0x20
ether 78:e4:00:ab:2a:86  txqueuelen 1000  (Ethernet)
RX packets 42085  bytes 26676847 (25.4 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 26140  bytes 6345384 (6.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1167994/comments/5


On 2015-05-29T09:29:43+00:00 Fedora wrote:

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer 

[Touch-packages] [Bug 539478] Re: pulseaudio crashed with SIGSEGV in pa_mainloop_prepare

[Bug Watch Updater]

** Changed in: pulseaudio (Fedora)
   Status: Unknown => Won't Fix

** Changed in: pulseaudio (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/539478

Title:
  pulseaudio crashed with SIGSEGV in pa_mainloop_prepare

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: pulseaudio

  On qjack launch, pulseaudio is killed with: pulseaudio -k and called
  with pulseaudio -DnF ./pulse/pulsejack.pa (attached)

  ProblemType: Crash
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vininim5002 F jackd
   /dev/snd/pcmC0D0c:   vininim5002 F...m jackd
   /dev/snd/pcmC0D0p:   vininim5002 F...m jackd
   /dev/snd/seq:vininim4575 F qjackctl.bin
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 22'
 Mixer name : 'Realtek ALC269'
 Components : 'HDA:10ec0269,10438398,0014'
 Controls  : 12
 Simple ctrls  : 7
  CheckboxSubmission: 3be1018555e5686649a0be4b157d89fe
  CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
  CrashCounter: 1
  Date: Tue Mar 16 07:32:19 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu12
  ProcCmdline: pulseaudio -DnF /home/username/.pulse/pulsejack.pa
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SegvAnalysis:
   Segfault happened at: 0xb6acaa : mov
0x37b(%eax),%eax
   PC (0x00b6acaa) ok
   source "0x37b(%eax)" (0xb227c28c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   jack_port_get_total_latency () from /usr/lib/libjack.so.0
   pa_sink_get_latency_within_thread ()
   pa_sink_process_msg () from /usr/lib/libpulsecore-0.9.21.so
   ?? () from /usr/lib/pulse-0.9.21/modules/module-jack-sink.so
   pa_asyncmsgq_dispatch ()
  Title: pulseaudio crashed with SIGSEGV in jack_port_get_total_latency()
  Uname: Linux 2.6.32-16-generic i686
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/539478/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1070006] Re: Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)

[Bug Watch Updater]

Launchpad has imported 38 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=533716.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-11-08T18:34:12+00:00 Need wrote:

My modem is not supported by Fedora rawhide. I have installed and run
usb_modeswitch. It now shows:

# lsusb
Bus 002 Device 005: ID 19d2:0031 ONDA Communication S.p.A. 

I have also added a new fdi file and rebooted:

# cat /usr/share/hal/fdi/information/20thirdparty/20-zte-mf636.fdi


   

  
 

GSM-07.07
GSM-07.05
modem

 
  
   


Unfortunately it does not seem to be detected by NetworkManager.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/0


On 2009-11-16T15:19:28+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 12 
development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/1


On 2009-11-25T14:10:13+00:00 robledo wrote:

I have found that with modem ZTE MF626, F12 automatically mounts a usb-
mass-storage device, and if ejected (while keeping the usb-modem
connected), the modem is recognized, and connections are possible.

Pls see output in bug report
https://bugzilla.redhat.com/show_bug.cgi?id=541314

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/2


On 2009-12-01T08:59:09+00:00 Dan wrote:

lsof, can you attach some 'dmesg' output from right when you plug the
device in, through when it's modeswitched, through when NM fails to
recognize the device?  I'd like to see if it's correctly modeswitched or
not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/3


On 2009-12-01T09:54:29+00:00 robledo wrote:

Dan, if you need output for the ZTE MF 626 (not 636), let me know.  Same
issue.  Pls give precise instructions on how to "dmesg", however.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/4


On 2009-12-01T22:36:03+00:00 Need wrote:

It's not modeswitched, I have to wrong the usb_modeswitch utility
manually with a custom config file. I will post the output before and
after tomorrow. Before the modeswitch the virtual cdrom is mounted.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/5


On 2009-12-01T22:49:55+00:00 Need wrote:

s/wrong/run/;

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/6


On 2009-12-01T22:57:20+00:00 robledo wrote:

Created attachment 375229
dmesg output for zte mf626


attached output from dmesg > ztemf626.log, when 1) attached usb modem ZTE MF 
626, 2) eject mass-storage device, leading to 3) recognition of mf 626 modem in 
NW, to 4) establish the 3G connection (disable wifi), and then 5) disconnect 
the 3G connection, and finally 6) try to reconnect the 3G connection. 
hope it helps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/7


On 2009-12-02T08:53:42+00:00 Need wrote:

I plug in the usb stick:

# dmesg -c
usb 2-2: new high speed USB device using ehci_hcd and address 5
usb 2-2: New USB device found, idVendor=19d2, idProduct=2000
usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-2: Product: ZTE CDMA Technologies MSM
usb 2-2: Manufacturer: ZTE, Incorporated
usb 2-2: configuration #1 chosen from 1 choice
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 7:0:0:0: CD-ROMZTE  USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 0
sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
sr 7:0:0:0: Attached scsi CD-ROM sr0
sr 7:0:0:0: Attached scsi generic sg1 type 5
ISO 9660 Extensions: Microsoft Joliet Level 1
ISOFS: changing to secondary root
SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts

# lsusb 
Bus 002 Device 005: ID 19d2:2000 ONDA 

[Touch-packages] [Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

[Daniel van Vugt]

I have put your two screenshots side by side, flipped, and zoomed in.
See attached.

It appears there is no difference in the window decoration edges
(although the different wallpaper colour behind makes them look
different).

There is definitely a change in the X button design that is now visible.

** Attachment added: "decor.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+attachment/4997372/+files/decor.png

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Triaged

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1727269

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome. This is really just a cosmetic issue. The window
  edges (mostly only top left) and window buttons were sharper and
  clearer in Ubuntu 16.04 und the versions before. The rough window
  egdges do not appear in all windows, it is especially obvious with
  Firfox. The impression with the buttons is always present.

  This is apparent in stock Ubuntu 17.10 on various laptops (Thinkpad
  x220, Acer Aspire 5253, Macbook Pro late 2010).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[PJSingh5000]

Note, when I run software-properties-gtk from the command line, here is
the output I receive whenever I click on a checkbox on the "Other
Software" tab.


$ software-properties-gtk
ERROR:root:Authentication canceled, changes have not been saved

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1727908

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  New

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727909] [NEW] Using Wayland

[Daniel C Aragao]

Public bug reported:

When I've put my pendrive system just close session and I go back to log in 
screen. It happens in very different ways.
Attached goes the logs file.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Oct 26 23:55:20 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
InstallationDate: Installed on 2017-10-19 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P06RCX.075.160311.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KW3BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 370E4K
dmi.product.version: P06RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful crash ubuntu wayland-session

** Attachment added: "Logs file"
   https://bugs.launchpad.net/bugs/1727909/+attachment/4997355/+files/error

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1727909

Title:
  Using Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When I've put my pendrive system just close session and I go back to log in 
screen. It happens in very different ways.
  Attached goes the logs file.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Oct 26 23:55:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
  InstallationDate: Installed on 2017-10-19 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1727908] [NEW] Software & Updates application does not permit changes on the "Other Software" tab

[PJSingh5000]

Public bug reported:


On the "Other Software" tab, I am unable to select "Canonical Partners".
Similarly, the other checkboxes on the "Other Software" can not be clicked.
Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

However, activating or deactivating checkboxes on other tabs causes an
authorization dialog to be presented to the user.

I experience this bug in an an Xorg session.

sources.list and sources.list.d have the following permissions:
-rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

All files in sources.list.d have the following permissions as this example:
-rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

$ apt-cache policy software-properties-gtk
software-properties-gtk:
  Installed: 0.96.24.17
  Candidate: 0.96.24.17
  Version table:
 *** 0.96.24.17 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: software-properties-gtk 0.96.24.17
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 26 22:45:09 2017
InstallationDate: Installed on 2017-10-26 (1 days ago)
InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1727908

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  New

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

[Daniel van Vugt]

"wayland" is just the protocol library, so not the right place to file
this.

The xorg-server package covers both native Xorg servers and Xwayland so
filing there... until someone finds somewhere more appropriate.


** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1726595

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in xorg-server package in Ubuntu:
  New

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1726595/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 240073] Re: Ifconfig uses inconsistent units

[Bug Watch Updater]

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=118006.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2004-03-10T23:13:26+00:00 Petri wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040122 Debian/1.6-1

Description of problem:
eth0  Link encap:Ethernet  HWaddr 00:02:B3:63:DA:BE
  inet addr:80.222.51.178  Bcast:80.222.63.255 Mask:255.255.240.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4643429 errors:0 dropped:0 overruns:0 frame:0
  TX packets:4407272 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:463857499 (442.3 Mb)  TX bytes:2823718271 (2692.9 Mb)

I think Mb (megabit = 1,000,000 bits) should be MiB (megabyte =
1,048,576 bytes).

Version-Release number of selected component (if applicable):
net-tools-1.60-22

How reproducible:
Always

Steps to Reproduce:
1. Use calculator: 2823718271 / 1024 / 1024 = 2692,90759182... MiB.
   1048576 * 2692,90759182 = 2823718271,00024832

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/0


On 2004-03-10T23:33:07+00:00 Juha wrote:

debian uses [KMG]iB

eth0  Link encap:Ethernet  HWaddr 00:50:04:6A:F7:3C  
  inet addr:10.0.0.10  Bcast:10.0.0.255  Mask:255.255.255.0
  inet6 addr: fe80::250:4ff:fe6a:f73c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2478006 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2866712 errors:0 dropped:0 overruns:0 carrier:0
  collisions:1706 txqueuelen:1000 
  RX bytes:795139352 (758.3 MiB)  TX bytes:3036864587 (2.8 GiB)

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/1


On 2004-03-14T18:03:38+00:00 Petri wrote:

man 7 units

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/2


On 2004-03-14T18:30:56+00:00 Tom wrote:

Created attachment 98528
Fix units to be SI standard

This fixes the unit issues, and adds support for units from KiB to EiB.

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/3


On 2004-06-18T18:01:59+00:00 Alan wrote:

KiB and MiB are geekspeek, it would IMHO be far better simply to
divide by 1000, 100 et and use KB MB. MiB etc are also don't seem
to be SI approved units but a proposal.


Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/5


On 2004-08-30T09:33:01+00:00 Radek wrote:

Tom's patch is applied to net-tools-1.60-33. I agree with Alan that
"i" units are quite strange, but according to SI and that some other
free software started to using them I've included this patch.

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/6


On 2006-01-08T01:12:54+00:00 David wrote:

To correct the misinformation in comment #4 above:

The prefixes for binary multiples are not just 'geekspeek', and neither are they
merely 'a proposal'. They have been an IEC standard since 1998.

See http://physics.nist.gov/cuu/Units/binary.html for further
background.

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/240073/comments/7


On 2009-04-28T01:54:05+00:00 Alexander wrote:

some more information:

The SI prefixes should only be used in the decimal sense: kilobyte and megabyte 
denote one thousand bytes and one million bytes respectively, while kibibyte 
and mebibyte denote 1024 bytes and 1,048,576 bytes respectively. This 
recommendation has been adopted by SI, IEEE, CIPM, NIST, ISO/IEC and some other 
leading national and international standards, which now state that the prefixes 
k, M and G should always refer to powers of ten, even in the context of 
information technology.
(reference: ISO/IEC IEC 8-13:2008 )

reduced timeline:
1998:
IEC introduces unambigous prefixes for binary multiples (KiB, MiB, GiB etc.), 
reserving kB, MB, GB and so on for their decimal sense.

2005:
IEC prefixes are adopted by the IEEE after a two-year trial period.

2008:
NIST guidelines require use of IEC prefixes KiB, MiB ... (and not kB, MB) for 
binary byte multiples

[Touch-packages] [Bug 260918] Re: needed: libv4l and associated application patches (or "gspca stopped working in 2.6.27")

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=456825.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-07-27T20:49:53+00:00 Hans wrote:

As you probably know I'm one of the authors of the v4l2 rewrite of the gspca usb
webcam driver framework (which supports more then 100 different cams), this v4l2
rewrite has been merged into the 2.6.27 kernel and thus will become available in
the official Linux kernel soon.

One of the parts of the v4l2 rewrite has been removing conversion from various
manufacturer cam specific video formats to more normal videoformats from the
drivers, as this really does not belong in userspace.

As a result of this the gspca subdrivers can generate raw video frames in the
following formats:

#define V4L2_PIX_FMT_SN9C10X  v4l2_fourcc('S', '9', '1', '0') /* SN9C10x
compressed bayer
#define V4L2_PIX_FMT_SPCA501  v4l2_fourcc('S', '5', '0', '1') /* YUYV per line 
#define V4L2_PIX_FMT_SPCA505  v4l2_fourcc('S', '5', '0', '5') /* YYUV per line 
#define V4L2_PIX_FMT_SPCA508  v4l2_fourcc('S', '5', '0', '8') /* YUVY per line 
#define V4L2_PIX_FMT_SPCA561  v4l2_fourcc('S', '5', '6', '1') /* compressed GBRG
bayer
#define V4L2_PIX_FMT_PAC207   v4l2_fourcc('P', '2', '0', '7') /* compressed BGGR
bayer

As we do not want to see each application implement (nor having to implement)
support for these various formats, as we like to have one code base and only one
code base for these formats. A library has been written (with me as the main
author) to convert from these formats to BGR24 or YUV420. For more on this
library see:
http://hansdegoede.livejournal.com/3636.html

The attached patch adds support to the gstreamer v4l2 plugin to use this library
if available on the system, it has also been submitted upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=545033

libv4l will show up in rawhide as soon as a cvsadmin gets around to creating a
cvs module for it, see libv4l'2 review request: bug 456772

Getting this patch into Fedora is important for the F-10 better webcam support
feature:
https://fedoraproject.org/wiki/Features/BetterWebcamSupport


###

A note about the patch, the patch is actually quite simple, as libv4l has been
designed for quick porting of existing apps to libv4l, for this reason libv4l
fully mimicks the raw /dev/video interface (and if no conversion is needed and
for non relevant calls like setting ctrl's, passes through all calls 
unmodified).

All that the patch does and all that needs to be changed to use libv4l is
replace the relevant xxx calls on /dev/video with v4l2_xxx calls.

The only special thing about the patch is that it passes the
V4L2_ENABLE_ENUM_FMT_EMULATION flag to libv4l2 on open, this patch tells libv4l2
to report the "emulated" formats in the ENUM_FMT ioctl results. Which libv4l2
does not do be default so that ENUM_FMT only reports the really supported
formats (a TRY_FMT with one of the 2 supported emulated formats can then be done
to see if conversion is supported for the specific device). Given the working of
the v4l2 plugin, enabling the ENUM_FMT emulation is needed.

I've successfully tested this patch with cheese and 2 spca561 cams (quite
popular IC, used by both logitech and creative), 2 pac207 cams (another quite
popular IC), 3 SN9C10X cams (also very popular) and 1 spca501 cam. All of which
do not work without this patch, as gstreamer does not support their proprietary
video formats (and rightfully so).

###

p.s.

While doing a local rpm testbuild of gstreamer-plugins-good with this patch, it
failed because it build a couple of plugins not in the %files list due to me
having to much foo-devel packages installed, can you please add:
"--disable-esd --disable-libcaca --disable-aalib" to the %configure flags to fix
this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/0


On 2008-07-27T20:49:53+00:00 Hans wrote:

Created attachment 312745
PATCH adding support for using libv4l to the v4l2 plugin

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/1


On 2008-07-28T09:28:03+00:00 Hans wrote:

libv4l has just been build for rawhide, and should show up in the next rawhide
push, in the mean time you can get it from koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57774


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/2


On 2008-07-28T13:45:56+00:00 Adam wrote:

Patch looks plausible, but I'm no expert.  I'm curious to see how the upstream
bug 

[Touch-packages] [Bug 426587] Re: Very large latency in gstreamer-based voip apps

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=521276.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-09-04T15:55:35+00:00 Matěj wrote:

Created attachment 359824
stderr from Empathy

Description of problem:
Frist I tried to make a call with Pidgin (XMPP/Jingle) and in one case (with 
upstream developer ;-)) I have managed to have a call. Except that my voice was 
approx. 15 sec delayed on the other side of the communication.

Same happened to me now when using Empathy with SIP.

Version-Release number of selected component (if applicable):
empathy-2.27.91.1-6.fc12.x86_64
telepathy-sofiasip-0.5.17-1.fc12.x86_64
gstreamer-plugins-good-0.10.16-1.fc12.x86_64
pidgin-2.6.1-1.0.mc.1.fc12.x86_64

How reproducible:
100%

Steps to Reproduce:
1.just use VoIP application using GStreamer
2.
3.
  
Actual results:
my voice is delayed for approx. 15 sec

Expected results:
delay in reasonable amount (less than few sec, I guess)

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/0


On 2009-09-08T17:11:43+00:00 Johan wrote:

This bug is fixed by the patch http://cgit.freedesktop.org/gstreamer
/gst-plugins-base/commit/?id=058776bcf1ab218b509d19685a0b528d71c65f98 .

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/1


On 2009-10-05T19:36:49+00:00 Fedora wrote:

gstreamer-0.10.25-1.fc11,gstreamer-plugins-base-0.10.25-1.fc11 has been 
submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/gstreamer-0.10.25-1.fc11,gstreamer-plugins-base-0.10.25-1.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/4


On 2009-10-07T03:14:19+00:00 Fedora wrote:

gstreamer-0.10.25-1.fc11, gstreamer-plugins-base-0.10.25-1.fc11 has been pushed 
to the Fedora 11 testing repository.  If problems still persist, please make 
note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gstreamer 
gstreamer-plugins-base'.  You can provide feedback for this update here: 
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10311

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/5


On 2009-10-07T10:48:57+00:00 Fedora wrote:

gstreamer-plugins-good-0.10.16-1.fc11 has been submitted as an update for 
Fedora 11.
http://admin.fedoraproject.org/updates/gstreamer-plugins-good-0.10.16-1.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/6


On 2009-10-09T03:39:09+00:00 Fedora wrote:

gstreamer-plugins-good-0.10.16-1.fc11 has been pushed to the Fedora 11 testing 
repository.  If problems still persist, please make note of it in this bug 
report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gstreamer-plugins-good'.  You 
can provide feedback for this update here: 
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10348

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/7


On 2009-10-15T16:42:37+00:00 Matěj wrote:

Yes, quality of the call is still unusable, but that's not GStreamer (or
PA) fault. This has been fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/8


On 2009-10-21T00:47:04+00:00 Fedora wrote:

gstreamer-0.10.25-1.fc11, gstreamer-plugins-base-0.10.25-1.fc11 has been
pushed to the Fedora 11 stable repository.  If problems still persist,
please make note of it in this bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/9


On 2009-10-27T06:54:55+00:00 Fedora wrote:

gstreamer-plugins-good-0.10.16-1.fc11 has been pushed to the Fedora 11
stable repository.  If problems still persist, please make note of it in
this bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/10


** Changed in: gst-plugins-base
   Importance: Unknown => High

-- 
You received this bug 

[Touch-packages] [Bug 610600] Re: Serious video performance regression in cheese (2.28.1->2.30.1)

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=507450.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-06-22T20:00:37+00:00 A. wrote:

Description of problem:
I have an asus eee 1000hd, with a built in webcam (according to kinfocenter it 
is from Vendor ID 0x4f2, Product ID 0xb071, Revision 15.44). The webcam works 
well (I used it recently for a video call with skype, under Fedora 10, and just 
recorded a  clip under windows XP. It also worls well under cheese as long as 
the "start recording" button is not pressed). However, when attempting to 
record video with cheese, once the button "start recording" is pressed, the 
video display within the cheese window goes dark, and afterwards, as the image 
reappears, it seems to do one frame per minute or so, and barely records any 
audio, which is of a totally useless quality.


Version-Release number of selected component (if applicable):
$ rpm -q cheese
cheese-2.26.2-1.fc11.i586


How reproducible:
every time

Steps to Reproduce:
1.start cheese
2.click video
3.click start recording
4.see how it breaks down, as above
5.also, check the resulting recording, and see how there is no useful output, 
perhaps only two or three frames and some clicking audio
  
Actual results:
useless recording, as per point 5 above

Expected results:
a useful ogv recording with 30 frames per second video at the chosen 
resolution, and useful audio, all in a ogv file.

Additional info:
I read some of the other bug reports on cheese, but couldn't find one that 
matched my bug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/0


On 2009-06-22T20:47:33+00:00 A. wrote:

I just updated to rwahide's cheese, and while the problem is less
severe, it is  still very much present, and the resulting video is still
useless. However, perhaps the developers are already onto improving
something, which needs to be continued, as I can see *some* improvement.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/1


On 2009-11-23T20:11:47+00:00 A. wrote:

I just updated to Fedora 12, and I still get the same problem. Recording
video with cheese is choppy and broken. I updated the distribution this
bug relates to, to Fedora 12.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/2


On 2010-09-21T10:41:36+00:00 Adam wrote:

closing as a dupe of the newer bug more informative 572169.

*** This bug has been marked as a duplicate of bug 572169 ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/21


** Changed in: cheese (Fedora)
   Status: Unknown => Invalid

** Changed in: cheese (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/610600

Title:
  Serious video performance regression in cheese (2.28.1->2.30.1)

Status in Cheese:
  Fix Released
Status in GStreamer:
  Fix Released
Status in OEM Priority Project:
  Won't Fix
Status in Release Notes for Ubuntu:
  Fix Released
Status in gstreamer0.10 package in Ubuntu:
  Won't Fix
Status in gstreamer0.10 source package in Lucid:
  Won't Fix
Status in gstreamer0.10 source package in Maverick:
  Won't Fix
Status in cheese package in Fedora:
  Invalid

Bug description:
  Binary package hint: cheese

  Ubuntu version: 10.04
  Cheese version: 2.30.1
  Hardware: Dell Latitude 2110 netbook - Intel Pinetrail CPU
  Settings: minimum resolution - 160x120

  Expected behavior: Start recording movie, recording starts promptly.

  Actual behavior:

  Screen is mostly frozen for ~14 seconds, and then recording appears to
  start tolerably.  Karmic's (2.28.1) performance was pretty poor, but
  the delay was around 4 seconds.

  To give the netbook a chance I set resolution to a minimum resolution.
  At higher resolutions, like 640x480, the machine just can't keep up at
  all.

  This has been observed on other hardware, and on a Core2Duo machine
  this startup performance is still very bad (though not quite so bad).
  Other apps, and gstreamer from the command line, do not seem to suffer
  the same problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 913839] Re: tether over bluetooth - regression in precise

[Bug Watch Updater]

Launchpad has imported 22 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1054212.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-01-16T13:10:40+00:00 Martin wrote:

Description of problem:
Pairing phone Control Center - Bluetooth device - phone fails when DUN service 
is selected

Version-Release number of selected component (if applicable):
control-center-3.8.6-5.el7.x86_64
bluez-4.101-12.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Control Center - Bluetooth - "+" to add device.
2. Select device from list - Continue
3. Confirm PIN
4. Check "Access the Internet using your mobile phone (DUN)"

Actual results:
Error: timed out detecting phone details.

Expected results:
Pairing setup is complete.

Additional info:

Jan 16 13:55:12 martin-holec bluetoothd[1002]: bluetoothd[1002]: Discovery 
session 0x7fec88f05870 with :1.245 activated
Jan 16 13:55:12 martin-holec bluetoothd[1002]: Discovery session 0x7fec88f05870 
with :1.245 activated
Jan 16 13:55:12 martin-holec gnome-session[3039]: Window manager warning: Buggy 
client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x283 
(Bluetooth )
Jan 16 13:55:12 martin-holec gnome-session[3039]: Window manager warning: 
meta_window_activate called by a pager with a 0 timestamp; the pager needs to 
be fixed.
Jan 16 13:55:14 martin-holec bluetoothd[1002]: bluetoothd[1002]: Stopping 
discovery
Jan 16 13:55:14 martin-holec bluetoothd[1002]: Stopping discovery
Jan 16 13:55:21 martin-holec dbus-daemon[1040]: dbus[1040]: [system] Rejected 
send message, 4 matched rules; type="method_return", sender=":1.245" (uid=1000 
pid=8719 comm="bluetooth-wizard ") interface="(unset)"
Jan 16 13:55:21 martin-holec dbus[1040]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.245" (uid=1000 pid=8719 
comm="bluetooth-wizard ") interface="(unset)" member="(unset)" e
Jan 16 13:55:22 martin-holec bluetoothd[1002]: bluetoothd[1002]: input-headset 
driver probe failed for device 5C:6B:32:13:5F:21
Jan 16 13:55:22 martin-holec bluetoothd[1002]: input-headset driver probe 
failed for device 5C:6B:32:13:5F:21
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 SyncMLClient
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 DialupNetworking
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 OBEXObjectPush
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 OBEXFileTransfer
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 AudioSource
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 A/V_RemoteControlTarget
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 A/V_RemoteControl
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 Headset_-_AG
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 HandsfreeAudioGateway
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 SyncMLClient
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 DialupNetworking
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 OBEXObjectPush
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 OBEXFileTransfer
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 AudioSource
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 A/V_RemoteControlTarget
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 A/V_RemoteControl
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 Headset_-_AG
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 HandsfreeAudioGateway
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 
5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: Default Bluetooth 
adapter is powered
Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_start: 
starting DUN device discovery...
Jan 16 13:55:23 martin-holec gnome-session[3039]: ** 

[Touch-packages] [Bug 1680421] Re: Computer suspends/sleeps before login

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1365719.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-08-10T03:02:47+00:00 Joachim wrote:

Description of problem:
For current Fedora 25, systemd causes a Lenovo ThinkPad T400 which is attached 
to a docking station (plus external monitor) with its lid closed to suspend 
after logging out from a GNOME session briefly after displaying the graphical 
login manager GDM. Upon pressing the power button in order to resume from 
suspend, it suspends again as soon as GDM has reappeared on the screen.

Version-Release number of selected component (if applicable):
systemd-231-3.fc25

How reproducible:
Always.

Steps to Reproduce:
1. Log out from GNOME session.

Actual results:
After briefly displaying the login manager, the system suspends.

Expected results:
The login manager is displayed, and it is possible to log in.

Additional info:
Switching to a virtual console after resume from suspend prevents the system 
from suspending again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1680421/comments/0


On 2016-08-10T13:16:33+00:00 Zbigniew wrote:

Sounds like some gdm issue. Can you attach the logs (journalctl -b)
output from around when this happens?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1680421/comments/1


On 2016-08-10T19:22:03+00:00 Joachim wrote:

Created attachment 1189785
Output of 'journalctl -b' for logout procedure

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1680421/comments/2


** Changed in: systemd
   Status: Unknown => Confirmed

** Changed in: systemd
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1680421

Title:
  Computer suspends/sleeps before login

Status in systemd:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  I am not able to login into the system because it sleeps in the boot
  process. To fix this, I need to edit (in recovery mode) the
  /etc/systemd/logind.conf to replace the following options:

  HandleLidSwitch=ignore
  HandleLidSwitchDocked=ignore

  This behaviour started in Ubuntu 14.10.

  Some other users have this issue too:
  
http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  6 08:25:20 2017
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405)
  MachineType: Positivo Positivo Mobile
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: M5X0V
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Positivo Mobile
  dmi.product.version: VT6198
  dmi.sys.vendor: Positivo
  mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1680421/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

[KEVIN KENNY]

Seth: Your requested output is perf-20171026.txt

It's not clear to me what's out of the ordinary in the stack
traces, except of course that once we're in the Python code
of 'apport', things have unquestionably already gone to Hell.
Maybe someone who's familiar with the code will have a better
idea.

** Attachment added: "perf-20171026.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4997295/+files/perf-20171026.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1690485

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 196277] Re: A GNOME login without keypress dosn't set GNOME keyboard settings

[Bug Watch Updater]

Launchpad has imported 18 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=447252.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-05-19T05:40:03+00:00 Ilya wrote:

Description of problem:

A keyboard layout bug. After boot strange characters entered from keyboard
instead proper ones. Also keyboard layout cannot be switched neither by
switchkey, nor through menu switcher. Default layout is US English, second
layout is Russian-winkeys. The proper layout can only be restored through
keyboard properties screen.

The attachment shows incorrect characters displayed just after bootup, with
layout indicator shows US English as the current layout.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/75


On 2008-05-19T05:40:03+00:00 Ilya wrote:

Created attachment 305899
screenshot showing the bug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/76


On 2008-05-19T06:15:07+00:00 Ilya wrote:

By the way, on the fresh system all worked well (FC9-release). The bug appeared
after I made updates from the Internet.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/77


On 2008-07-03T17:14:31+00:00 Milan wrote:

*** Bug 449305 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/136


On 2008-07-03T17:21:44+00:00 Milan wrote:

I'm not sure what component should be selected for this bug. I hit the same
problem. After a restart I have to go to the keyboard setting through keyboard
applet and change something (deleting and adding keymap). Then keyboard
switching works then again. I'm using default GNOME session.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/137


On 2008-07-03T22:14:33+00:00 Ilya wrote:

I think official Fedora notes should mention that languages other than English 
are not fully supported. Otherwise all people who use another language would 
think Fedora is a very buggy system.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/138


On 2008-07-24T09:31:20+00:00 Simos wrote:

This bug appears to be similar to

keyboard layout switching shortcut doesn't work after reboot
https://bugs.launchpad.net/bugs/196277

Could you please verify that you have enabled autologin on your system?

If this is the case, then it would be better to change the report title to
"Autologin in GNOME disables keyboard layout switching"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/166


On 2008-07-24T09:40:00+00:00 Alexey wrote:

As i know fedora 9 do not have autologin feature because xserver.1.4.9 do not
support it anymore.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/167


On 2008-07-24T10:01:30+00:00 Ilya wrote:

You're wrong. It has no GUI for autologin to switch on, but I enabled autologin 
through config files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/170


On 2008-07-24T11:36:56+00:00 Simos wrote:

I am not familiar with Fedora; in Ubuntu there is an option in
System/Administration/Login Window/Security/Enable Automatic Login.

What this actually does is it tells GDM to let a specific user in by default.
Essentially, it's a GDM option in Ubuntu.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/172


On 2008-07-29T05:03:29+00:00 Peter wrote:

There are two separate issues here (from what I can tell so far).

One is that the keymap with autologin is different before and after the first
key has been pressed (when the keyboard is evdev anyway).

The other one is that gnome is incapable of setting the xkb map correctly.
Specifying layouts in HAL's fdi file or the xorg.conf works fine, including the
switcher applet.

I'm still trying to figure out why the second happens.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/180

[Touch-packages] [Bug 417757] Re: [regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups

[Bug Watch Updater]

** Changed in: glibc (Fedora)
   Status: Confirmed => Fix Released

** Changed in: glibc (Fedora)
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/417757

Title:
  [regression] all network apps / browsers suffer from multi-second
  delays by default due to IPv6 DNS lookups

Status in eglibc package in Ubuntu:
  Invalid
Status in eglibc source package in Lucid:
  Won't Fix
Status in eglibc source package in Karmic:
  Fix Released
Status in glibc package in Fedora:
  Fix Released

Bug description:
  In Karmic, DNS lookups take a very long time with some routers,
  because glibc's DNS resolver tries to do IPv6 () lookups even if
  there are no (non-loopback) IPv6 interfaces configured. Routers which
  do not repond to this cause the lookup to take 20 seconds (until the
  IPv6 query times out).

  *** PLEASE DO NOT COMMENT ON THIS BUG unless you have something
  constructive to say. Everything that can be said has already been
  said, and if you comment, you are just adding noise. Please let those
  that actually know what they are doing concentrate on fixing this bug
  from now on. ***

  If disabling IPv6 or using good DNS servers like openDNS fixes the
  problem, you are not dealing with this bug. Please refrain from
  complaining here in that case

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/417757/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

[KEVIN KENNY]

The plot thickens.

The configuration of the build appears to be partially implicated.
Could it be that with your ./configure flags, it's failing to find a 
failing PAM or something?

When I build with the ./configure that you suggested, it works.
When I build with dpkg-buildpackage, on the same source code, it fails.

Output from the failing case, with your patch to add debug output,
attached as sshd-strace-20171026.txt



** Attachment added: "sshd-strace-20171026.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4997275/+files/sshd-strace-20171026.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1690485

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 58430] Re: Command-line recovery required when fsck reports an unexpectedy inconsistency

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=462804.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-09-19T00:56:17+00:00 Olivier wrote:

When fsck on boot fails, it dumps the user into a shell.. and unless he
is a Unix sysadmin, he will be lost.

Solution: Replace the current message with something like:

Repairing your file system may cause errors!!! Do you want to: [F]orce
Repair, get to a [S]hell or [R]eboot:

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/58430/comments/13


On 2008-09-19T01:01:28+00:00 Bill wrote:

1) Just rebooting when fsck fails is ... going to fail again. That's not useful.
2) If it fails to the point when you get a shell, forcing a fsck won't work - 
it dies because -y doesn't work.

Which leaves dropping to a shell, which is what we do.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/58430/comments/14


On 2008-09-19T01:25:30+00:00 Jack wrote:

Still, this is a moment of utter panic and confusion for anyone
inexperienced with fsck. That's a lot of desktop Linux users. (Won't
anyone think of the grandmothers!) The present interface simply abandons
the user; it needs to be more guiding. If a fsck -y fails, then it
should explain why it failed, what files might be gone, or if all hope
is lost...

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/58430/comments/15


On 2008-09-19T01:51:25+00:00 Olivier wrote:

1) Rebooting can be useful if you want to reboot onto something else (a
usb key or a rescue network boot or whatever and for some reason you
can't directly access the power key).. alright, not that useful..

1.1) I agree we need to keep the current "drop me to a shell" for the
few people who understand debugfs and other exciting tools.

2) It currently doesn't try -y, it tries -a ... which will only do "safe
repairs", -y can often help. (unless -y is in /fsckoptions..)

3) Even if -y fails, there should really be more help.

For the the case I had today (using F9), the user got it working just by
doing "fsck /dev/" and answering "y" a few times, so -y would have
definitely worked.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/58430/comments/16


On 2008-09-19T08:25:18+00:00 Sitsofe wrote:

Whenever I've tried to "repair" a filesystem using fsck -y the
filesystem has been destroyed and would no longer even get to /bin/bash
the next time round. In my experience if the system is asking you this
question you are already in trouble and at a bare minimum you have to
understand what /lost+found means.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/58430/comments/17


On 2009-06-10T02:45:06+00:00 Bug wrote:


This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/58430/comments/18


On 2009-06-10T15:46:16+00:00 Bill wrote:

I'm still not sure what sort of useful guiding information could be here
that doesn't 

[Touch-packages] [Bug 66104] Re: [Gutsy] scim: input freezes in various applications under XIM mode

[Bug Watch Updater]

Launchpad has imported 25 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=201284.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2006-08-04T00:55:49+00:00 Leon wrote:

Description of problem:
Sometimes a KDE app will not accept inputs anymore (even input method is not
activated). The only thing I can do to have input again is change to "Simple
Composing Input Method" which is a test input method module in Qt, or restart
the application.

How reproducible:
not everytime

Steps to Reproduce:
1. Use a KDE app long enough
  
Actual results:
No inputs were outputted

Expected results:
Output english letters

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/0


On 2006-08-08T05:56:02+00:00 Jens wrote:

Yep, I think I saw this on KDE desktop while testing this morning.

Need to test with another IM to see if it is a kde/qt problem or
issue with scim.  XIM seems to work fine with other apps.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/1


On 2006-08-15T02:21:29+00:00 Leon wrote:

Reproducible in FC6 devel using the following test case by Choe Hwanjin:

1. $ export XMODIFIERS=@im=SCIM
2. $ export GTK_IM_MODULE=xim
3. $ gedit/kedit
4. press ctrl-N
5. try to type something

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/2


On 2006-08-15T02:54:45+00:00 Jens wrote:

See 
http://sourceforge.net/mailarchive/forum.php?thread_id=30112584_id=43684
for more details.  It seems like that this is a xorg-x11 regression according to
discussion there.


Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/3


On 2006-08-15T09:42:37+00:00 Jens wrote:

Reproduced on fc5 and fc6.  RHEL4 and fc4 seem ok.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/4


On 2006-08-17T13:29:34+00:00 Jens wrote:

gedit loops with kinput2 and uim xim on rawhide.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/5


On 2006-08-18T15:12:13+00:00 Kevin wrote:

Adding upstream bug from the thread referred to in comment #3 above for 
tracking:
  https://bugs.freedesktop.org/show_bug.cgi?id=7869


Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/6


On 2006-08-19T05:38:37+00:00 Jens wrote:

(Problem also occurs with gcin fwiw.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/7


On 2006-08-19T10:03:40+00:00 Jens wrote:

I'm not easily able to reproduce the problem on kde apps.

A workaround for gtk xim at least seems to be to set "/FrontEnd/X11/Dynamic = 
true"
in .scim/config (but that breaks deadkey support under XIM direct input).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/8


On 2006-08-20T04:21:13+00:00 Jens wrote:

This can also easily be reproduced with kinput2 and gedit.

1. setup kinpu2 and restart desktop
2. run gedit
3. activate kinput2 with Shift-Space and press Ctrl-n

at this point gedit goes into a hard loop.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/9


On 2006-08-20T09:38:51+00:00 Jens wrote:

Also reproduced with libX11-0.99.3 fwiw.

Here is a backtrace of where gedit loops with kinput2:

#0  XIfEvent (dpy=0x6ca790, event=0x7fff84fd6000, 
predicate=0x2ab427a0 <_CheckCMEvent>, arg=0x10b4000 " \220ݪ�*")
at IfEvent.c:58
#1  0x2ab42cea in _XimXRead (im=0x10b4000, recv_buf=0x7fff84fd61f0 "", 
buf_len=2048, ret_len=0x7fff84fd6144) at imTrX.c:446
#2  0x2ab45f86 in _XimReadData (im=0x10b4000, len=0x7fff84fd61a6, 
buf=0x7fff84fd61f0 "", buf_size=2048) at imTransR.c:154
#3  0x2ab46323 in _XimRead (im=0x10b4000, len=0x7fff84fd71fe, 
buf=0x7fff84fd61f0 "", buf_size=2048, 
predicate=0x2ab48c20 <_XimSyncCheck>, arg=0x10b8800 
"\200\217ݪ�*")
at imTransR.c:231
#4  0x2ab49d0e in _XimForwardEvent (ic=0x10b8800, ev=0x7fff84fd7290, 
sync=1) at imDefLkup.c:296
#5  0x2ab39c8b in 

[Touch-packages] [Bug 201078] Re: libelf.h can't be included

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=377241.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-11-12T08:18:49+00:00 Tom wrote:

Description of problem:

The libelf.h header now uses off64_t instead of off_t in various places, but it
does nothing to ensure that such a type is defined leading to failed compilation
of any code which uses libelf.h without defining _LARGEFILE64_SOURCE.

Version-Release number of selected component (if applicable):

elfutils-libelf-devel-0.130-3.fc8.x86_64

How reproducible:

Happens every time.

Steps to Reproduce:
1. Try and compile a C source file containing #include 
  
Actual results:

Compile fails.

Expected results:

Compile works.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/0


On 2007-11-12T08:32:55+00:00 Roland wrote:

Note that in prior versions, programs built without -D_FILE_OFFSET_BITS=64 on
32-bit machines were buggy if they used the Elf_Data type directly.  So if you
want to work correctly with a variety of elfutils-devel versions, using that
setting is the best plan.

I will replace off64_t with loff_t in the header for the next version.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/1


On 2007-12-19T03:10:15+00:00 Roland wrote:

*** Bug 426100 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/2


On 2008-01-24T21:48:54+00:00 Fedora wrote:

elfutils-0.132-3.fc8 has been pushed to the Fedora 8 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update elfutils'

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/3


On 2008-01-24T21:53:47+00:00 Fedora wrote:

elfutils-0.132-3.fc7 has been pushed to the Fedora 7 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update elfutils'

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/4


On 2008-03-01T21:48:26+00:00 Fedora wrote:

elfutils-0.133-1.fc8 has been submitted as an update for Fedora 8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/5


On 2008-05-21T19:48:51+00:00 Fedora wrote:

elfutils-0.135-1.fc7 has been submitted as an update for Fedora 7

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/8


On 2008-05-21T19:51:25+00:00 Fedora wrote:

elfutils-0.135-1.fc8 has been submitted as an update for Fedora 8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/9


On 2008-05-21T19:52:55+00:00 Fedora wrote:

elfutils-0.135-1.fc9 has been submitted as an update for Fedora 9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/10


On 2008-05-29T02:39:43+00:00 Fedora wrote:

elfutils-0.135-1.fc7 has been pushed to the Fedora 7 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update elfutils'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/F7/FEDORA-2008-4457

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/11


On 2008-07-30T20:08:25+00:00 Fedora wrote:

elfutils-0.135-1.fc9 has been pushed to the Fedora 9 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/201078/comments/12


On 2008-07-30T20:11:37+00:00 Fedora wrote:

elfutils-0.135-1.fc8 has been pushed to the Fedora 8 

[Touch-packages] [Bug 192651] Re: hardy sudo path is always reset

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=489744.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-11T16:28:08+00:00 Jeff wrote:

Description of problem:
Our users have a pretty scary PATH variable and they have a script named 
runasrelease that does:
sudo -u release bash -c "$*"

Since upgrading to fedora10+, the PATH variable is cleared and set to
whatever was builtin with --secure-path. This breaks our expected usage
of sudo as it removes PATH which we want set.

Adding:
!env_reset

or env_reset
env_keep = "HOME PATH"

does not work.

Version-Release number of selected component (if applicable):
sudo-1.6.9p17-6

How reproducible:
PATH=$PATH:/tmp/pathtest
sudo -u anyotheruser bash -c 'echo $PATH'

Steps to Reproduce:
jschroeder@ops2.fra03: ~ $ echo $PATH
/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/java/bin:/home/release:/home/release/scripts:/opt/mysql/5.1.30/bin:/home/jschroeder/bin
jschroeder@ops2.fra03: ~ $ sudo -u release bash -c 'echo $PATH'
[sudo] password for jschroeder: 
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin

Actual results:
PATH is cleared due to the --secure-path option

Expected results:
There should be a way for PATH to not be cleared. !env_reset or adding PATH to 
env_keep should work. This is fixed in 1.7.0 according to upstream.

Additional info:

* Wed May 14 2008 Peter Vrabec  1.6.9p13-6
- compiled with secure path (#80215)

https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/192651 ubuntu bug
http://www.gratisoft.us/bugzilla/show_bug.cgi?id=284 upstream bug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/192651/comments/5


On 2009-05-12T12:07:41+00:00 Fedora wrote:

sudo-1.7.1-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/sudo-1.7.1-1.fc11

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/192651/comments/6


On 2009-05-13T00:23:37+00:00 Fedora wrote:

sudo-1.7.1-1.fc11 has been pushed to the Fedora 11 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update sudo'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-4879

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/192651/comments/8


On 2009-06-09T12:08:45+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 11 
development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/192651/comments/10


On 2009-06-16T01:57:40+00:00 Fedora wrote:

sudo-1.7.1-1.fc11 has been pushed to the Fedora 11 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/192651/comments/11


** Changed in: sudo (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/192651

Title:
  hardy sudo path is always reset

Status in sudo:
  Fix Released
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo package in Fedora:
  Fix Released

Bug description:
  Binary package hint: sudo

  According to /usr/share/doc/sudo/OPTIONS, sudo is bulit with

  --with-secure-
  
path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin"

  This is basically ok, but you should be able to change the default
  PATH for sudo.

  I tried in sudoers:

  Defaultsenv_reset
  Defaultsenv_keep="HOME"

  and

  Defaults!env_reset

  But PATH is always reset to the configured one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/192651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=492208.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-25T21:44:28+00:00 Jeremy wrote:

Description of problem:
When connecting to VPN with NetworkManager-vpnc, it sets the default route to 
the VPN device.  When I connect with "vpnc" it leaves the default route alone.

There are also a couple of other routes missing when I use
NetworkManager to connect.

Version-Release number of selected component (if applicable):
NetworkManager-vpnc-0.7.0.99-1.fc10.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Connect to vpn
2.Check route with "route"
3.
  
Actual results:
0.0.0.0 0.0.0.0 0.0.0.0 U 0  00 tun0

Expected results:
0.0.0.0 192.168.1.1 0.0.0.0 UG0  00 wlan0

Additional info:
The diff between the vpnc routing and the NetworkManager-vpnc routing is:
--- vpnc2009-03-25 14:38:59.629563747 -0700
+++ nwman   2009-03-25 14:39:25.283537596 -0700
@@ -1,7 +1,5 @@
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse Iface
-10.yy.yy.yy 0.0.0.0 255.255.255.255 UH0  00 tun0
-10.zz.zz.zz 0.0.0.0 255.255.255.255 UH0  00 tun0
 xx.xx.xx.xx 192.168.1.1 255.255.255.255 UGH   0  00 wlan0
 192.168.1.0 0.0.0.0 255.255.255.0   U 2  00 wlan0
 10.69.148.0 0.0.0.0 255.255.255.0   U 0  00 tun0
@@ -32,4 +30,4 @@
 10.224.0.0  0.0.0.0 255.224.0.0 U 0  00 tun0
 10.0.0.00.0.0.0 255.192.0.0 U 0  00 tun0
 10.128.0.0  0.0.0.0 255.192.0.0 U 0  00 tun0
-0.0.0.0 192.168.1.1 0.0.0.0 UG0  00 wlan0
+0.0.0.0 0.0.0.0 0.0.0.0 U 0  00 tun0

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/5


On 2009-04-03T23:16:23+00:00 vaxon wrote:

Same problem here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/7


On 2009-04-04T00:22:18+00:00 vaxon wrote:

Actually, looking a bit more at the vpn configuration I can tell that
it's all configurable.

Click on the Network Manager icon and choose "VPN Connections" -> "Configure 
VPN...". Then choose the connection name and click "Edit". Go to "IPv4 
Settings" tab and click the "Routes" button at the lower-right corner.
Check off "Use this connection only for resources on its network".
This should make vpn use the old default route instead of redirecting all 
traffic to tun0.
Additional routes can be set up here as well.

But I really think that leaving the default route intact should be the
default vpnc behaviour.

Thanks,
Vax.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/8


On 2009-05-01T10:43:16+00:00 Stephen wrote:

I have a very similar problem here. But I cannot work around it using
the technique mentioned in #2 because that box is not checked.

When I connect using vpnc from the command line my name servers are
correctly tunnelled down tun0 as in the bug description. However when I
connect using NetworkManager-vpnc (default settings, and in fact every
combination of settings I have tried so far) my name servers are not
send down tun0 and consequently I cannot access any internal systems.

NetworkManager-vpnc should have the same behaviour as the vpnc command
line client.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/16


On 2009-05-01T17:54:02+00:00 Jeremy wrote:

(In reply to comment #2)
> But I really think that leaving the default route intact should be the default
> vpnc behaviour.

It must be a behaviour change, because it used to work OK.  Anyway,
checking that box does fix the problem for me.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/17


On 2009-11-05T14:33:37+00:00 Don wrote:

Confirmed that checking the box fixes the problem here as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/25

[Touch-packages] [Bug 269429] Re: pycrypto-2.0.1 uses md5 & sha1 modules which will be deprecated in 2.6/3.0

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=484473.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-02-07T00:02:55+00:00 Henrik wrote:

Description of problem:

Applications using python-crypto may get the following warning:

/usr/lib64/python2.6/site-packages/Crypto/Hash/SHA.py:6: DeprecationWarning: 
the sha module is deprecated; use the hashlib module instead
  from sha import *
/usr/lib64/python2.6/site-packages/Crypto/Hash/MD5.py:6: DeprecationWarning: 
the md5 module is deprecated; use hashlib instead
  from md5 import *

Version-Release number of selected component (if applicable):

python-crypto-2.0.1-14.1.x86_64
python-2.6-4.fc11.x86_64


How reproducible:

Always

Steps to Reproduce:
1. 
2.
3.
  
Actual results:

/usr/lib64/python2.6/site-packages/Crypto/Hash/SHA.py:6: DeprecationWarning: 
the sha module is deprecated; use the hashlib module instead
  from sha import *
/usr/lib64/python2.6/site-packages/Crypto/Hash/MD5.py:6: DeprecationWarning: 
the md5 module is deprecated; use hashlib instead
  from md5 import *


Expected results:

No warnings about deprecated functions.

Additional info:

>From a quick grep it also applies to Crypto/Hash/HMAC.py


It seems the fix is simply changing as follows

From:
 from md5 import *
 import mf5
To:
 from hashlib import md5

and similar for SHA.

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/5


On 2009-02-07T14:39:09+00:00 Stewart wrote:

Can you confirm this is fixed in 2.0.1-15? I haven't setup my rawhide VM
to test yet...

http://koji.fedoraproject.org/koji/taskinfo?taskID=208

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/6


On 2009-02-07T16:33:18+00:00 Henrik wrote:

Same problem in 2.0.1-15.

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/7


On 2009-02-07T16:36:57+00:00 Henrik wrote:

The patch in CVS looks about right, but is not added to the spec file so
not part of the build..

Needs to be both a Patch0: source line, and a %patch0 statement in %prep

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/8


On 2009-02-07T18:07:31+00:00 Stewart wrote:

Sorry about that, fixed now. Rebuilding now:
http://koji.fedoraproject.org/koji/taskinfo?taskID=411

I've also changed the patch a bit, as to remain compatible with PEP 247
we can't simply replace the md5/sha modules with their hashlib
equivalents - hashlib provides a function and not a module with the
digest_size and blocksize properties. The SHA and MD5 functions will now
contain the correct values for digest_size and blocksize (the same
values as the objects from hashlib have) as before there were hardcoded
from the Python sha and md5 modules.

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/9


On 2009-02-12T19:10:22+00:00 Thorsten wrote:

Stewart, upstream has a report reg. this as well:

 https://bugs.launchpad.net/pycrypto/+bug/269429

There are also fixes in git:

 
http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.x.git;a=commitdiff;h=d2311689910240e425741a546576129f4c9735e2
 
http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.x.git;a=commitdiff;h=84b793416b52311643bfd456a454afbfb5da

Should we use those just to be on the safe side?

BTW: Steward, would you be interested to take over python-crypto? I
don#t need it anymore

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/10


On 2009-02-18T19:25:26+00:00 Stewart wrote:

Fixed in 2.0.1-17:
http://koji.fedoraproject.org/koji/buildinfo?buildID=82882

Reply at: https://bugs.launchpad.net/pycrypto/+bug/269429/comments/11


** Changed in: python-crypto (Fedora)
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-crypto in Ubuntu.
https://bugs.launchpad.net/bugs/269429

Title:
  pycrypto-2.0.1 uses md5 & sha1 modules which will be deprecated in
  2.6/3.0

Status in Bazaar:
  Fix Released
Status in Python-Crypto:
  Fix Released
Status in python-crypto package in Ubuntu:
  Fix Released
Status in python-crypto package in Fedora:
  Fix Released

Bug description:
  This is only a very minor bug (and 2.6 hasn't even been released yet),
  but since the deprecations show up for every 

[Touch-packages] [Bug 375852] Re: sqllite doesn't support tables with names such as release or savepoint

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=481189.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-01-22T17:04:46+00:00 Nicholas wrote:

Description of problem:
Yum fails with latest sqlite 3.6.10 in rawhide.

Version-Release number of selected component (if applicable):
yum-3.2.21-3

How reproducible:
Always

Steps to Reproduce:
1. Update to new sqlite.
2. Remove /var/cache/yum directory.
3. Run a yum update.
  
Actual results:
It fetches the primary dbs for all the repos and then returns the following 
error:
Error: malformed database schema (removals) - no such table: main.packages

Expected results:
Update without error.

Additional info:
Yum works as expected if you revert to the previous sqlite-3.6.7, so it is 
definitely some change in the sqlite api.

There is also an issue with local repositories created with createrepo. I had a 
local repository in my repos.d and it causes the following error:
localrepo   

  | 1.0 kB 00:00
localrepo/primary   

  |  27 kB 00:00

(process:5225): GLib-CRITICAL **: g_timer_stop: assertion `timer !=
NULL' failed

(process:5225): GLib-CRITICAL **: g_timer_destroy: assertion `timer != NULL' 
failed
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in 
yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 229, in user_main
errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 104, in main
result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 339, in doCommands
self._getTs(needTsRemove)
  File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 101, in _getTs
self._getTsInfo(remove_only)
  File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 112, in 
_getTsInfo
pkgSack = self.pkgSack
  File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 592, in 
pkgSack = property(fget=lambda self: self._getSacks(),
  File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 435, in 
_getSacks
self.repos.populateSack(which=repos)
  File "/usr/lib/python2.6/site-packages/yum/repos.py", line 251, in 
populateSack
sack.populate(repo, mdtype, callback, cacheonly)
  File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 184, in populate
dobj = repo_cache_function(xml, csum)
  File "/usr/lib64/python2.6/site-packages/sqlitecachec.py", line 45, in 
getPrimary
self.repoid))
TypeError: Can not create packages table: near "release": syntax error

Again, when I revert to the previous sqlite 3.6.7, yum works as
expected.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/375852/comments/0


On 2009-01-22T17:45:58+00:00 Tom wrote:

It also "works for me" if I leave the new sqlite update but revert the
new fedora-release.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/375852/comments/1


On 2009-01-22T19:01:19+00:00 James wrote:

Tom can you make sure that's true ... do a:

yum list sqlite yum fedora-release
sha1sum /var/cache/yum/rawhide/*

...both before and after?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/375852/comments/2


On 2009-01-22T19:02:38+00:00 James wrote:

rpm -q if the yum list doesn't work.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/375852/comments/3


On 2009-01-22T19:11:07+00:00 Tom wrote:

Uhhh..

No, I was mistaken.  Sorry.

Appears I had backed out both fedora-release and sqlite at the same
time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/375852/comments/4


On 2009-01-22T19:42:16+00:00 Panu wrote:

This is sqlite bug alright, see
http://www.mail-archive.com/sqlite-users@sqlite.org/msg39666.html

My bad (insufficient testing), apologies. Will fix right away.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/375852/comments/5


On 2009-01-22T19:57:02+00:00 seth wrote:

[Touch-packages] [Bug 486005] Re: init: don't hold /dev/console open

[Bug Watch Updater]

Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=491474.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-21T14:33:13+00:00 Volodymyr wrote:

Description of problem:

SAK (Alt-SysRq-K) is no longer working in X. When this combination is
pressed to restart X server, system just hangs, without even syncing to
disk, display is corrupted, magic key is not working.

Workaround:

If you need to login into server or workstation from graphical console,
you can switch to text console tty2..tty6, use SAK to clean console from
any malicious software, which is left by previous user, then login into
system, verify owner of GDM and X processes or just kill them, then
switch back to tty1 and login into system using graphical console.


How reproducible:

Always.


Steps to Reproduce:
1. Boot Fedora in graphic mode.
2. Press Alt-SysRq-K

  
Actual results:

System is hangs without syncing to disk due to kernel panic: "Kernel
panic - not syncing: Attempted to kill init!"


Expected results:

X server and GDM are restarted.

Reply at: https://bugs.launchpad.net/upstart/+bug/486005/comments/0


On 2009-11-18T11:34:22+00:00 Bug wrote:


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/upstart/+bug/486005/comments/1


On 2009-11-18T17:54:27+00:00 Jani wrote:

This still happens with F12, please see
https://bugzilla.redhat.com/show_bug.cgi?id=528260

Reply at: https://bugs.launchpad.net/upstart/+bug/486005/comments/2


On 2009-11-19T11:19:03+00:00 Volodymyr wrote:

Nice example of racism in Open Source.

Yes, this bug is still exists in Fedora 11/12.

Reply at: https://bugs.launchpad.net/upstart/+bug/486005/comments/3


On 2009-11-19T18:40:14+00:00 Daniel wrote:

Strange. I didn't get any mails about being assigned this bug, never
seen it before.

First question: Are you really running initng? The bug is classified as
initng, but I see nothing in the description that indicates that initng
is really used. If you ARE using initng, I can recommend switching to
upstart as initng isn't maintained all that much anymore.

Reply at: https://bugs.launchpad.net/upstart/+bug/486005/comments/4


On 2009-11-20T00:52:16+00:00 Volodymyr wrote:

Currently, I use upstart-0.3.11-1.fc11.i586 on my notebook.

Problem is not in initialization subsystem itself: init, initng or
upstart. Problem in configuration of init subsystem and/or kernel
behaviour.

When SysRQ-K combination (SAK) is pressed on tty1, *kernel* kills *all*
processes on this tty, including all daemons, including init process,
and then hangs because init process is killed. It is *bad idea* to use
SAK on tty1.

In public environment (e.g. computer class in school) SAK is highly
recommended, otherwise smart child will leave slightly modified version
of GDM left running and will fool next user.

Unfortunately, X servers is moved from tty7 to tty1, so there is no
other protection from smart children except reboot.

To fix that problem, upstart must be configured to use any other tty
except tty1 for X server. Moreover, 

[Touch-packages] [Bug 611715] Re: mii-tool not working with e1000e nic driver

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=491358.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-20T15:44:24+00:00 Bill wrote:

Description of problem:

[root@apone ~]# mii-tool eth0
SIOCGMIIREG on eth0 failed: Input/output error
eth0: negotiated 100baseTx-FD, link ok

It reports the 'negotiated 100base...' line no matter whether or not
something is connected. This breaks the initscripts link check.

I suppose it could also be a kernel issue. Driver is:
[root@apone ~]# ethtool -i eth0
driver: e1000e
version: 0.3.3.3-k6

Also occurs on rawhide.

Version-Release number of selected component (if applicable):

net-tools-1.60-91.fc10.x86_64
kernel-2.6.28-4.fc10.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/611715/comments/0


On 2009-07-02T18:14:09+00:00 Andy wrote:


when mii-tool checks link status, this code is called (from mii-tool.c):

200 int show_basic_mii(int sock, int phy_id)
201 {
202 char buf[100];
203 int i, mii_val[32];
204 int bmcr, bmsr, advert, lkpar;
205
206 /* Some bits in the BMSR are latched, but we can't rely on being
207the only reader, so only the current values are meaningful */
208 mdio_read(sock, MII_BMSR);
209 for (i = 0; i < ((verbose > 1) ? 32 : 8); i++)
210 mii_val[i] = mdio_read(sock, i);
211
212 if (mii_val[MII_BMCR] == 0x) {
213 fprintf(stderr, "  No MII transceiver present!.\n");
214 return -1;
215 }

Since 'verbose' is false, we will call the SIOCGMIIREG ioctl with the
commands MII_BMSR and then the commands 0-7 will be called.  Those
commands are:


#define MII_BMCR0x00/* Basic mode control register */
#define MII_BMSR0x01/* Basic mode status register  */
#define MII_PHYSID1 0x02/* PHYS ID 1   */
#define MII_PHYSID2 0x03/* PHYS ID 2   */
#define MII_ADVERTISE   0x04/* Advertisement control reg   */
#define MII_LPA 0x05/* Link partner ability reg*/
#define MII_EXPANSION   0x06/* Expansion register  */
#define MII_CTRL10000x09/* 1000BASE-T control  */

Where is 0x7

If we look at the sources for e1000e, we can see why -EIO is returned.
>From drivers/net/e1000e/netdev.c (e1000_mii_ioctl) in net-next-2.6
upstream tree:

   4347 case SIOCGMIIREG:
   4348 if (!capable(CAP_NET_ADMIN))
   4349 return -EPERM;
   4350 switch (data->reg_num & 0x1F) {
   4351 case MII_BMCR:
   4352 data->val_out = adapter->phy_regs.bmcr;
   4353 break;
   4354 case MII_BMSR:
   4355 data->val_out = adapter->phy_regs.bmsr;
   4356 break;
   4357 case MII_PHYSID1:
   4358 data->val_out = (adapter->hw.phy.id >> 16);
   4359 break;
   4360 case MII_PHYSID2:
   4361 data->val_out = (adapter->hw.phy.id & 0x);
   4362 break;
   4363 case MII_ADVERTISE:
   4364 data->val_out = adapter->phy_regs.advertise;
   4365 break;
   4366 case MII_LPA:
   4367 data->val_out = adapter->phy_regs.lpa;
   4368 break;
   4369 case MII_EXPANSION:
   4370 data->val_out = adapter->phy_regs.expansion;
   4371 break;
   4372 case MII_CTRL1000:
   4373 data->val_out = adapter->phy_regs.ctrl1000;
   4374 break;
   4375 case MII_STAT1000:
   4376 data->val_out = adapter->phy_regs.stat1000;
   4377 break;
   4378 case MII_ESTATUS:
   4379 data->val_out = adapter->phy_regs.estatus;
   4380 break;
   4381 default:
   4382 return -EIO;
   4383 }
   4384 break;

The killer is 0x7 -- it seems it should not be checked by mii-tool.

My guess is that this would fail on multiple devices.  Have you tried it
with any other interfaces?

Reply at: https://bugs.launchpad.net/ubuntu/+source/net-
tools/+bug/611715/comments/1

[Touch-packages] [Bug 416150] Re: [enhancement] change default port

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=174032.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2005-11-23T23:00:36+00:00 Ian wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 
Fedora/1.7.12-1.5.1

Description of problem:
In some cases, tracepath continues tracing although it has already reached the 
intended destination host.  For example:

[vaj4088@coyote ~]$ tracepath 24.221.130.104
 1:  192.168.0.241 (192.168.0.241)  0.314ms pmtu 1500
 1:  firewall (192.168.0.250)   0.578ms
 2:  10.253.1.1 (10.253.1.1)  asymm  3  84.814ms
 3:  aztutmrt01.az.sprintbbd.net (24.221.129.1)   asymm  2  93.968ms
 4:   (24.221.130.104)   asymm  5 162.687ms
 5:  no reply
 6:  no reply
 7:  no reply
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
31:  no reply
 Too many hops: pmtu 1500
 Resume: pmtu 1500
[vaj4088@coyote ~]$  

tracepath should have stopped at the line labeled "4:", but continued
on.

 is a name from my /etc/hosts file that has been deleted to
protect the name of an innocent bystander.

Version-Release number of selected component (if applicable):
iputils-20020927-22

How reproducible:
Always

Steps to Reproduce:
My example shows how I reproduce the problem.  Networks being what they are, I 
don't know how to reproduce it in your circumstances.
  

Actual Results:  See description.

Expected Results:  Should have looked something like:

[vaj4088@coyote ~]$ tracepath 24.221.130.104
 1:  192.168.0.241 (192.168.0.241)  0.314ms pmtu 1500
 1:  firewall (192.168.0.250)   0.578ms
 2:  10.253.1.1 (10.253.1.1)  asymm  3  84.814ms
 3:  aztutmrt01.az.sprintbbd.net (24.221.129.1)   asymm  2  93.968ms
 4:   (24.221.130.104)   asymm  5 162.687ms
 Resume: pmtu 1500 hops 4 back 3
[vaj4088@coyote ~]$  


Additional info:

Note that the following works fine:

[vaj4088@coyote ~]$ tracepath 24.221.129.1
 1:  192.168.0.241 (192.168.0.241)  0.342ms pmtu 1500
 1:  firewall (192.168.0.250)   0.581ms
 2:  10.253.1.1 (10.253.1.1)  asymm  3 121.557ms
 3:  aztutmrt01.az.sprintbbd.net (24.221.129.1)   asymm  2 223.267ms 
reached
 Resume: pmtu 1500 hops 3 back 2
[vaj4088@coyote ~]$

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/0


On 2006-06-27T18:38:36+00:00 Daniel wrote:

Created attachment 131624
This patch changes the default destination port number to 33434 (which was 
assigned by IANA for tracerouting) and fixes the bug in a simple but functional 
way :]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/1


On 2006-07-02T23:06:31+00:00 Ian wrote:

(In reply to comment #1)
> This patch changes the default destination port number to 33434 (which was
> assigned by IANA for tracerouting) and fixes the bug in a simple but 
> functional
> way :]
> 

Dan -
Thanks for the effort, but I can set the port number on the command line and I
still get the same result if I choose 33434 as the port number.
This is using Fedora Core 5, which takes the command as
tracepath 24.221.130.104/33434

I think that the root cause needs to be understood and corrected.
Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/2


On 2006-07-03T10:41:13+00:00 Daniel wrote:

(In reply to comment #2)
> (In reply to comment #1)
> > This patch changes the default destination port number to 33434 (which was
> > assigned by IANA for tracerouting) and fixes the bug in a simple but 
functional
> > way :]
> > 
> 
> Dan -
> Thanks for the effort, but I can set the port number on the command line and I
> still get the same result if I choose 33434 as the port number.
> This is using Fedora Core 5, which takes the command as
> tracepath 24.221.130.104/33434
> 
> I think that the root cause needs to be understood and corrected.
> Thanks!

Yes, I know that the port number is not a solution to your problem. It's only 

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Bug Watch Updater]

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1380803.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-09-30T15:03:37+00:00 Alan wrote:

Description of problem:
Running "ip link show" outputs Message Truncated several times and the 
resulting interface list is incomplete.

The issue occurs when the number of VF interfaces is over ~50.

This is impacting applications/scripts which rely on parsing the output
of ip to ascertain the current network configuration (e.g. ovirt/vdsm)

Version-Release number of selected component (if applicable):
iproute-3.10.0-54.el7_2.1.x86_64


This appears to be related to 
https://bugzilla.redhat.com/show_bug.cgi?id=1086512

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/0


On 2016-10-26T10:59:36+00:00 Alan wrote:

This has been fixed upstream in either 4.5 or 4.6.

Rebuilding the SRPM from Fedora 25 (iproute-4.6.0-1.fc25.src.rpm) fixes
the problem. But iproute-4.4.0-3.fc24.src.rpm from Fedora 24 does not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/1


On 2017-01-11T02:42:06+00:00 Hangbin wrote:

commit 72b365e8e0fd5efe1d5c05d04c25950736635cfb
Author: Phil Sutter 
Date:   Fri Mar 4 19:57:28 2016 +0100

libnetlink: Double the dump buffer size

There have been reports about 'ip addr' printing "Message truncated" on
systems with large numbers of VFs. Although I haven't been able to get
my hands on hardware suitable to reproduce this, increasing the dump
buffer has been reported to resolve the issue. For want of a better
idea, just double the buffer size to 32k.

Feels like this opportunistic buffer size selection is rather
workarounding a design flaw in libnetlink or maybe even the netlink
protocol itself.

Signed-off-by: Phil Sutter 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/2


On 2017-03-24T10:32:00+00:00 Alan wrote:

If there's any interest I could probably provide access to a system
exhibiting the issue (Cisco B200 with VIC1340).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/3


On 2017-07-05T15:37:23+00:00 Alan wrote:

It seems that increasing the buffer size has simply pushed the problem
further up. With ~95 VFs the message truncated warnings return.

On my Cisco UCS platform it's possible to go as high as 114 VFs, while
other configurations support up to 223.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/4


On 2017-07-21T12:23:31+00:00 Phil wrote:

Hi Alan,

(In reply to Alan Griffiths from comment #5)
> It seems that increasing the buffer size has simply pushed the problem
> further up. With ~95 VFs the message truncated warnings return.
> 
> On my Cisco UCS platform it's possible to go as high as 114 VFs, while other
> configurations support up to 223.

So you see the problem even with iproute-4.6.0-1.fc25?

Thanks, Phil

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/5


On 2017-07-25T11:17:34+00:00 Alan wrote:

Yes, so the behaviour seems to be the same across the releases now.

I've tested: -

iproute-3.10.0-74 (EL7)
iproute-4.6.0-1 (FC25)
iproute-4.11.0-1 (FC26)

The test system has 2 PF. At 90 x VF all above versions work, at 91 x VF
I start seeing message truncated errors.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/comments/6


On 2017-10-10T11:53:00+00:00 Jan wrote:

Just a note:

There are theoretical and practical upper limits to the number of
Virtual Functions per PF (256 from some sources)[1], so setting a static
maximum buffer size is a justifiable option. That moves the burden over
to ensuring that the response per VF doesn't grow in the future.

Libvirt had similar issues (it used libnl) until it enabled message
peeking by default.  Unfortunately the only way to solve this issue in
all cases without performance penalty is to alter the kernel's message
truncation handling mechanism to not free the skb if MSG_TRUNC occurred.
[1]

It's possible to put in a retry on truncation, resizing the receive
buffer to fit the response, BUT 

[Touch-packages] [Bug 1727888] Re: systemd-udevd crashed with SIGABRT in __libc_open64()

[Apport retracing service]

*** This bug is a duplicate of bug 1715782 ***
https://bugs.launchpad.net/bugs/1715782

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1715782, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997252/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997255/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997262/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997264/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997265/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997266/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727888/+attachment/4997267/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1715782

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727888

Title:
  systemd-udevd crashed with SIGABRT in __libc_open64()

Status in systemd package in Ubuntu:
  New

Bug description:
  Não sei o que aconteceu.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 26 22:02:18 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-10-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Gigabyte Technology Co., Ltd. Z170MX-Gaming 5
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=dc17a66f-fa09-4bd5-9abe-81385461c4a4 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_open64 (file=0x563a3c7822b0 "/dev/sdd", oflag=657408) at 
../sysdeps/unix/sysv/linux/open64.c:46
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __libc_open64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF21:bd03/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727888/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: Fix Released => Confirmed

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Released => Confirmed

** Changed in: systemd (Ubuntu Zesty)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Released => Confirmed

** Changed in: systemd (Ubuntu Artful)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * Incomplete cherrypick of ARP functionality in networkd resulted in
  an undesired side-effect, specifically NOARP flag started to be
  applied unconditionally, specifically when it should not have,
  resulting in loss of network connectivity.

  * This is a regression in -updates.

  [Test Case]

   * Configure a bond using networkd
   * Upgrade
   * Make sure NOARP flag is not set on the interfaces / bond

  [Regression Potential]

   * This is an upstream fix for this issue.

  [Other Info]
   
   * Upstream fix
  
https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
   
   * Original bug report

  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Dimitri John Ledkov]

aha, i need to specify anything that requires to call the code path to
adjust any flags from non default.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Incomplete cherrypick of ARP functionality in networkd resulted in
  an undesired side-effect, specifically NOARP flag started to be
  applied unconditionally, specifically when it should not have,
  resulting in loss of network connectivity.

  * This is a regression in -updates.

  [Test Case]

   * Configure a bond using networkd
   * Upgrade
   * Make sure NOARP flag is not set on the interfaces / bond

  [Regression Potential]

   * This is an upstream fix for this issue.

  [Other Info]
   
   * Upstream fix
  
https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
   
   * Original bug report

  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727158] Re: lscpu shows incorrect instantaneous CPU MHz value

[Doug Smythies]

This is not a bug, the change was done on purpose. What is displayed
here and under /proc/cpuinfo has changed. For Intel processors it simply
displays tsc now.

One of several upstream references for this is:
https://bugzilla.kernel.org/show_bug.cgi?id=197153

If you want to observe your current CPU frequencies do this:

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq


** Bug watch added: Linux Kernel Bug Tracker #197153
   https://bugzilla.kernel.org/show_bug.cgi?id=197153

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1727158

Title:
  lscpu shows incorrect instantaneous CPU MHz value

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10:

  lscpu has the following fields of interest to this report:

  Model name:  Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz

  CPU MHz: 3499.996
  CPU max MHz: 5900.
  CPU min MHz: 1600.

  The CPU MHz field is incorrect:  At idle it never shows down-step, and
  at full load, it never shows the CPU's boost frequency (which should
  be up to about 4.6GHz on my system).

  This was working correctly under Ubuntu 17.04, showing the full range
  between 1600 and 4600.  But with Ubuntu 17.10 it remains constantly at
  the CPU's design spec of 3499.996.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 22:00:02 2017
  InstallationDate: Installed on 2017-09-01 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 183729] Re: compat: utmp not cleared on tty logout

[Bug Watch Updater]

Launchpad has imported 30 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=470004.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-11-05T07:49:18+00:00 Michal wrote:

Description of problem:
If user switches to terminal (Ctrl+Alt+Fx) use it and then exits, this terminal 
stays listed in sessions to switch to


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.switch to terminal (Ctrl+Alt+F2)
2.enter username and password
3.logout
4.kde->switch user
  
Actual results:
"user: TTY login (vt2)" is listed even if session has been already terminated

Expected results:
only active sessions are listed

Additional info:
if you repeat above steps, you can achieve "user: TTY login (vt2)" to be listed 
twice (three times, four...)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/9


On 2008-11-05T13:55:13+00:00 Rex wrote:

Confirmed.

Interesting, I wonder by what method kde uses to determine users logged
into tty's... either that's broken or console logins are.

"last" gives interesting results for me:
rdieter1 tty2 ... Wed nov 5 08:52   gone - no logout

except, I *did* logout.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/10


On 2008-11-07T17:45:28+00:00 Rex wrote:

OK, looks like tty logins never finish logging out.  For me, ALT-F2 goto
console, login... do stuff... logout... stuck, no login: prompt

Now, who to blame for this? :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/11


On 2008-11-07T17:46:45+00:00 Rex wrote:

bouncing over to util-linux-ng (owner of login), in hopes of some
insight.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/12


On 2008-11-25T17:50:35+00:00 Rex wrote:

Interesting, I can't reproduce anymore, how about you?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/13


On 2008-11-26T04:48:14+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 10 
development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/14


On 2008-11-26T09:29:26+00:00 Michal wrote:

I'm in work now, where I have kde 4.1.3 packages from updates-testing
and it doesn't work for me. Still the "same" problem.

I think there is (maybe) one difference: If I try to switch user via
"start"->Switch user and select tty console, it starts new session with
kdm as if I select "start new session". If I try to switch via screen
saver lock or via kdm, it "works" as usual. I don't know if this is new
change or if it was working this way already.

I can test also on system updated without updates-testing today later if
you want.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/15


On 2009-01-30T14:57:39+00:00 Rex wrote:

I take back comment #4, console logins are still not registerring
logout, 'last' still reports only 'gone - no logout'

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/183729/comments/16


On 2009-03-19T13:19:46+00:00 Karel wrote:

It seems that /sbin/init from upstart does not care about utmp at all.

(Note that mingetty(8) and login(1) can create a new utmp entry on systems
where init(8) is broken, but init(8) has to set the entry to DEAD_PROCESS
state when user logout and login process has exited).

See utmp man page:

  The first entries ever created result from init(8) processing inittab(5).
  Before an entry is processed, though, init(8) cleans up utmp by setting
  ut_type to DEAD_PROCESS, clearing ut_user, ut_host, and ut_time with null
  bytes for each record which ut_type is not DEAD_PROCESS or RUN_LVL and where
  no process with PID ut_pid exists. If no empty record with the needed ut_id
  can be found, init(8) creates a new one. It sets ut_id from the inittab,
  ut_pid and ut_time to the current values, and ut_type to INIT_PROCESS.

  mingetty(8) (or agetty(8)) locates the 

[Touch-packages] [Bug 298241] Re: Apple CUPS Daemon: unauthenticated SIGSEGV crash via RSS subscriptions

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=473901.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-12-01T13:03:13+00:00 Jan wrote:

Common Vulnerabilities and Exposures assigned an identifier CVE-2008-5183 to
the following vulnerability:

cupsd in CUPS before 1.3.8 allows local users, and possibly remote
attackers, to cause a denial of service (daemon crash) by adding a
large number of RSS Subscriptions, which triggers a NULL pointer
dereference.  NOTE: this issue can be triggered remotely by leveraging
CVE-2008-5184.

References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5183
http://www.gnucitizen.org/blog/pwning-ubuntu-via-cups/
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241
http://www.openwall.com/lists/oss-security/2008/11/19/3
http://www.openwall.com/lists/oss-security/2008/11/19/4

Patch: See attachment -- cups-1.3-max-subscriptions.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/6


On 2008-12-03T13:03:29+00:00 Fedora wrote:

cups-1.3.9-4.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/cups-1.3.9-4.fc10

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/8


On 2008-12-03T13:05:29+00:00 Fedora wrote:

cups-1.3.9-2.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/cups-1.3.9-2.fc9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/9


On 2008-12-03T13:19:04+00:00 Fedora wrote:

cups-1.3.9-2.fc8 has been submitted as an update for Fedora 8.
http://admin.fedoraproject.org/updates/cups-1.3.9-2.fc8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/10


On 2008-12-09T11:33:00+00:00 Fedora wrote:

cups-1.3.9-4.fc10 has been pushed to the Fedora 10 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/12


On 2008-12-09T11:35:46+00:00 Fedora wrote:

cups-1.3.9-2.fc9 has been pushed to the Fedora 9 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/13


On 2008-12-09T11:38:24+00:00 Fedora wrote:

cups-1.3.9-2.fc8 has been pushed to the Fedora 8 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/14


On 2010-03-29T08:40:07+00:00 Tomas wrote:

https://www.redhat.com/security/data/cve/CVE-2008-5183.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/19


On 2010-12-24T02:14:14+00:00 Vincent wrote:

This was addressed via:

Red Hat Enterprise Linux version 5 (RHSA-2008:1029)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/298241/comments/20


** Changed in: cups (Fedora)
   Status: Confirmed => Fix Released

** Changed in: cups (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/298241

Title:
  Apple CUPS Daemon: unauthenticated SIGSEGV crash via RSS subscriptions

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Gutsy:
  Fix Released
Status in cups source package in Hardy:
  Fix Released
Status in cups package in Debian:
  Fix Released
Status in cups package in Fedora:
  Fix Released
Status in cups package in openSUSE:
  New

Bug description:
  Binary package hint: cups

  The CUPS daemon (/usr/sbin/cupsd) which listens by default on port
  631/tcp, crashes when more than 100 RSS Subscriptions are added. No
  authentication is required to perform such action. The caveat is that
  by default - at least on Ubuntu and openSuse - the daemon only accepts
  connections from localhost as specified by the default configuration
  settings (/etc/cups/cupsd.conf). However, the attack can be of remote
  nature by tricking the victim user to 

[Touch-packages] [Bug 331428] Re: crash when right clicking on a calendar entry

[Bug Watch Updater]

Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=477343.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-12-20T19:27:05+00:00 David wrote:

Created attachment 327551
gecko-bugreport.txt generated with crash described

Description of problem:

Thunderbird crashes with attached gecko bugreport while using lightning
extension. It is reproducable with certain existing events but also
happened when exporting the calendar to an ICS file.

Version-Release number of selected component (if applicable):

[settle ~/] 4% rpm -q thunderbird thunderbird-lightning
thunderbird-2.0.0.18-1.fc10.i386
thunderbird-lightning-0.9-3.fc10.i386


How reproducible:

Open a specific event in my calendar to edit. not all events, just some.  Also 
happened this morning when exporting one calendar to an ICS file.
 
Steps to Reproduce:
1. open thunderbird and switch to calendar mode
2. select file->export calendar, select calendar, press Ok.
3. choose file name and location, select iCalendar format, press "save"
4. crash 
  
Actual results:

crash with attached gecko-bugreport.txt file.

Expected results:

save the file in iCalendar format and return to program.

Additional info:

exporting to an HTML file doesn't cause the same crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/0


On 2008-12-20T19:30:59+00:00 David wrote:

Created attachment 327552
gecko-bugreport.txt generated with crash after editing an event

This gecko-bugreport.txt file was generated after editing an event and
closing the window with the window manager close button.  not all events
cause the crash but there isn't anything special about the event that
does cause the crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/1


On 2008-12-28T11:02:40+00:00 Lubomir wrote:

It's probably either ICAL with unsupported features or broken; but
libical definitely shouldn't abort here anyways. I'm building a
replacement package with aborts on such conditions disabled.

Until it builds -- could you please install debugging symbols ("yum
install yum-utils; debuginfo-install libical sunbird") and reproduce the
problem again? We'd get a backtrace that would let us know more to find
out what's wrong with your calendar.

Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/2


On 2008-12-28T11:47:56+00:00 Lubomir wrote:

This is the package where the fatal aborts should be disabled, so you
will probably see an error message in thunderbird, but no crash:

http://koji.fedoraproject.org/koji/taskinfo?taskID=1023481

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/3


On 2008-12-28T20:57:59+00:00 David wrote:

(In reply to comment #2)
> It's probably either ICAL with unsupported features or broken; but libical
> definitely shouldn't abort here anyways. I'm building a replacement package
> with aborts on such conditions disabled.
> 
> Until it builds -- could you please install debugging symbols ("yum install
> yum-utils; debuginfo-install libical sunbird") and reproduce the problem 
> again?
> We'd get a backtrace that would let us know more to find out what's wrong with
> your calendar.
> 
> Thanks!

since i haven't installed any debug packages yet this will be a ~176MB
download to get installed.  if this will still be useful i can do it
when i have better connectivity tomorrow.  please let me know.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/4


On 2008-12-29T22:54:31+00:00 David wrote:

Created attachment 327937
gecko-bugreport.txt from crash after installing debuginfo rpms

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/5


On 2008-12-29T22:58:27+00:00 David wrote:

(In reply to comment #4)
> (In reply to comment #2)
> > It's probably either ICAL with unsupported features or broken; but libical
> > definitely shouldn't abort here anyways. I'm building a replacement package
> > with aborts on such conditions disabled.
> > 
> > Until it builds -- could you please install debugging symbols ("yum install
> > yum-utils; debuginfo-install libical sunbird") and reproduce the problem 
> > again?
> > We'd get a backtrace that would let us 

[Touch-packages] [Bug 306362] Re: Default D-Bus system bus policy is allow

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=474895.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-12-05T20:32:08+00:00 Colin wrote:

See:
https://bugs.freedesktop.org/show_bug.cgi?id=18229

Reply at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/306362/comments/41


On 2008-12-05T20:32:59+00:00 Fedora wrote:

dbus-1.2.6-1.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/dbus-1.2.6-1.fc10

Reply at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/306362/comments/42


On 2008-12-05T20:36:02+00:00 Fedora wrote:

dbus-1.2.6-1.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/dbus-1.2.6-1.fc10

Reply at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/306362/comments/43


On 2008-12-07T04:12:09+00:00 Fedora wrote:

dbus-1.2.6-1.fc10 has been pushed to the Fedora 10 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/306362/comments/44


On 2008-12-07T04:32:11+00:00 Fedora wrote:

dbus-1.2.6-1.fc9 has been pushed to the Fedora 9 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/306362/comments/45


On 2008-12-08T17:53:49+00:00 Feng wrote:

This version of dbus messes up everything:

gpk stops working,
system-config-services stops working,
system-config-printer stops working,

and more.

Seems like some default policy were changed, and the corresponding
system components were not tweaked.


Refer to this link:

http://forums.fedoraforum.org/showthread.php?t=206797

Reply at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/306362/comments/55


** Changed in: dbus (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/306362

Title:
  Default D-Bus system bus policy is allow

Status in D-Bus:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in dbus package in Debian:
  Fix Released
Status in dbus package in Fedora:
  Fix Released

Bug description:
  A new security release of DBus is now available:

  http://dbus.freedesktop.org/dbus/releases/dbus-1.2.6.tar.gz

  This release contains a (partial, see below) fix for:
  https://bugs.freedesktop.org/show_bug.cgi?id=18229

  == Summary ==

  Joachim Breitner discovered a mistake in the default configuration for the
  system bus (system.conf) which made the default policy for both sent and
  received messages effectively *allow*, and not deny as intended.

  This release fixes the send side permission, but does not change the receive.
  See below for more details.

  == Available workarounds ==

  Add explicit  rules to existing policy files which do not
  already have them.

  == Mitigating factors ==

  There are three important mitigating factors.

  * First, in an examination of a Fedora 10 system, many services contained
  explicit  rules under the "default" context. These deny rules did (and
  continue to) operate as expected.

  * Second, an increasing trend has been for core system services to use
  PolicyKit, or otherwise do security checks on the service side.  Any system
  which relies on PolicyKit is unaffected by this flaw.

  * Third, the SELinux DBus support is not affected by this flaw.

  Now, as mentioned above this fix is partial.  DBus has two kinds of policy
  permissions, send and receive.  Generally speaking, the send side permission 
is
  much more important.  However, DBus has supported receive side permissions for
  a few reasons, among those are:

  * Ensuring signals containing sensitive data aren't visible by unexpected
  processes.  Suggested fix: Do not put sensitive data in DBus signals; use
  targeted method calls.

  * A way for processes to "second-pass" filter messages before they reach their
  C code.  Suggested fix: Something like PolicyKit (or just manual service-side
  permission checks) remain a better way to do this.

  For compatibility reasons, this release only fixes the send-side permission
  check, and not receive.  A greater number of services will need to be updated
  for a future 

[Touch-packages] [Bug 306310] Re: Resume (from memory) goes back to sleep automatically

[Bug Watch Updater]

** Changed in: linux
   Status: In Progress => Fix Released

** Changed in: linux
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/306310

Title:
  Resume (from memory) goes back to sleep automatically

Status in gnome-power:
  Invalid
Status in Linux:
  Fix Released
Status in acpi-support package in Ubuntu:
  Fix Released
Status in gnome-power-manager package in Ubuntu:
  Fix Released
Status in hal package in Ubuntu:
  Invalid
Status in pm-utils package in Ubuntu:
  Invalid
Status in acpi-support source package in Jaunty:
  Fix Released
Status in gnome-power-manager source package in Jaunty:
  Fix Released
Status in hal source package in Jaunty:
  Invalid
Status in pm-utils source package in Jaunty:
  Invalid

Bug description:
  Upon resuming from suspend-to-RAM, the system will start to wake, and
  will immediately go back to sleep.  If I cycle it one or two times
  more, it will stay awake.  I have reproduced this exact behavior with
  Jaunty on the new kernel as well as on Fedora 10
  (https://bugzilla.redhat.com/show_bug.cgi?id=475585), so it is not
  specific to Ubuntu.

  It has been observed that this happens when suspending via hotkey but
  not when suspending command (details in comments, below).

  As a conjecture, it is behaving as if due to some race condition it
  has not yet cleared  that it has a suspend event, so it immediately
  re-processes the suspend upon waking.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-2-generic 2.6.28-2.3
  ProcCmdLine: root=UUID=ac4ccc70-26e3-44dd-a6cf-715d1226eeb4 ro quiet
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-2.3-generic
  SourcePackage: linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/306310/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 487997] Re: Compose key not working in Qt apps in Gnome

[Bug Watch Updater]

Launchpad has imported 39 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=468590.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-10-26T14:34:10+00:00 Flóki wrote:

Description of problem:
IS keyboard in kde applications is not working.
Icelandic characters áéóú are not possible to input with keyboard in gnome.
 

Version-Release number of selected component (if applicable):
kdesdk-4.1.2-4.fc10.x86_64

How reproducible:
always

Steps to Reproduce:
1.
log in use gnome and icelandc keyboard
2.
start kate  type á 
3.

  
Actual results:
´a

Expected results:
á

Additional info:
This works in FC9,  and when selecting KDE session when login inn after setting 
keyboard in kde

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/0


On 2008-10-26T23:02:20+00:00 Kevin wrote:

This sounds like a regression from the new X11 keyboard input mechanism
(it now uses the "evdev" driver instead of the "kbd" driver). But I have
no idea if it's X11's, Qt's or kdelibs's fault.

What appears to be happening is that something is enabling the
nodeadkeys option somewhere.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/1


On 2008-10-29T11:15:47+00:00 Kevin wrote:

*** Bug 468977 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/2


On 2008-11-26T04:15:30+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 10 
development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/3


On 2008-12-09T17:30:08+00:00 Louis-Philippe wrote:

Same problem here, although it's in reverse : doesn't work in GNOME
native applications in a GNOME environment but works in KDE applications
in GNOME environment.

How reproducible:
always

Steps to Reproduce:
1.
log in use gnome and canadian multilingual keyboard
2.
start gedit  type á
3.
Actual results:
´a

Expected results:
á

4. start kwrite type á
Actual results:
á

Expected results:
á

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/4


On 2009-01-04T19:03:30+00:00 Kevin wrote:

*** Bug 477552 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/5


On 2009-01-04T19:05:07+00:00 Kevin wrote:

Looks like this also affects Qt-only apps (see duplicate).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/6


On 2009-01-04T21:01:17+00:00 Simos wrote:

GTK+ applications have their own copy of the compose sequence table, so
in a default GNOME environment (without SCIM, without setting the
GTK_IM_MODULE variable), dead keys should work irrespective of other
settings.

Last time I checked for QT applications, they look up the XOrg compose
table files, which are located at /usr/share/X11/locale, and the file
chosen depends on your current locale.

See the discussion at bug 477552 for some more hints.

In my case (I have GNOME/Ubuntu 8.10/partial installation of QT apps), accents 
work.
When I use 'strace' on a QT app, I get

access("/usr/share/X11/locale/el_GR.UTF-8/Compose", R_OK) = 0

which shows that the compose file is read successfully for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/487997/comments/7


On 2009-01-05T01:33:47+00:00 Flóki wrote:

I have not noticed this bug in Ubuntu 8.10.
I tried strace for kwrite and gedit in GNOME and kwrite in KDE.


Results from strace
In gnome kwrite  
strace -Ff -tt kwrite 2>&1 | tee strace_kwrite.log
[floki@flokip ~]$ cat strace_kwrite.log | grep /usr/share/X11/locale/
00:15:12.406207 open("/usr/share/X11/locale/locale.alias", O_RDONLY) = 8
00:15:12.410857 open("/usr/share/X11/locale/locale.alias", O_RDONLY) = 8
00:15:12.414368 open("/usr/share/X11/locale/locale.dir", O_RDONLY) = 8
00:15:12.415913 access("/usr/share/X11/locale/en_US.UTF-8/XLC_LOCALE", R_OK) = 0
00:15:12.416026 

[Touch-packages] [Bug 387091] Re: openssh-server should broadcast availability via avahi

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=475996.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-12-11T14:11:37+00:00 Bastien wrote:

Avahi should set the TXT record for the SSH service it exports to
include the public key of the SSH server (in a manner compatible with
MacOS X, which does the same thing).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/0


On 2008-12-11T19:48:16+00:00 Lennart wrote:

Uh. This is not the appropriate place to report this.

To do this properly we should patch OpenSSH to do the Avahi registration
itself. But I fear the OpenSSH would not be willing to merge such a
patch. Right now we do mDNS/DNS-SD publishing of the SSH service by
dropping a static service definition file in /etc/avahi. It's just an
xml file. Including the SSH server key in that file automatically is not
really possible.

I am reassigning this now to ssh, let's see what the ssh maintainers
have to say about this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/1


On 2008-12-11T20:09:58+00:00 Tomas wrote:

I don't know much about the potential avahi registration code, that
means what dependencies it would bring to openssh and so on.

But I am really afraid this code would not be accepted upstream
especially if some of the dependencies would be GPL licensed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/2


On 2008-12-12T17:57:54+00:00 Lennart wrote:

It would pull in libavahi-client which is LGPL. la-c pulls in D-Bus.
Which is GPL & Academic.

Also, that dependency would be completely optional.

I'd expect a refusal however due to more fundamental issues. i.e. mDNS
/DNS-SD is this unreliable, untrusted protocol that is used to spam the
local network about the existance of a service. Security people tend to
stay away from technology like that and normally don't see the
usefulness of this.

Yes, i know, I am not selling this very well right now Let's hope I
am mistaken.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/3


On 2009-03-10T09:20:31+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/4


On 2009-03-10T10:17:40+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/5


On 2009-03-10T10:19:37+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/6


On 2009-06-09T10:14:24+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 11 
development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/7


On 2009-09-24T08:51:48+00:00 Jan wrote:

This bug already has been fixed by static avahi registration.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/10


On 2009-09-25T10:11:02+00:00 Bastien wrote:

Not sure what you mean by that, but key certainly isn't exported using 
openssh-5.2p1-28.fc12.x86_64:
$ avahi-browse -ar
= eth0 IPv4 cookieSSH Remote Terminal  
local
   hostname = [cookie.local]
   address = [192.168.1.140]
   port = [22]
   txt = []

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/387091/comments/11


On 2009-10-18T12:39:05+00:00 Jan wrote:

It is exactly the same as MacOS exported.

Reply at:

[Touch-packages] [Bug 1433329] Re: Xorg without root rights

[Bug Watch Updater]

Launchpad has imported 27 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1078902.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-03-20T14:02:17+00:00 Jaroslav wrote:

This is a tracking bug for Change: Xorg without root rights
For more details, see: 
http://fedoraproject.org//wiki/Changes/XorgWithoutRootRights

The Xorg xserver is a large piece of software which currently runs as
root, making it a potential vector for attacks against the system. With
recent changes made to systemd-logind it is possible for the xserver to
let systemd-logind do device management for it, at which point the
xserver will no longer need root rights. Initially this will likely be
implemented as the xserver dropping root rights early on.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/0


On 2014-07-04T10:43:34+00:00 Jaroslav wrote:

This message is a reminder that Fedora 21 Accepted Changes Freeze
Deadline is on 2014-07-08 [1].

At this point, all accepted Changes should be substantially complete,
and testable. Additionally, if a change is to be enabled by default, it
must be so enabled at Change Freeze.

This bug should be set to the MODIFIED state to indicate that it
achieved completeness. Status will be provided to FESCo right after the
deadline. If, for any reasons, your Change is not in required state, let
me know and we will try to find solution. For Changes you decide to
cancel/move to the next release, please use the NEW status and set
needinfo on me and it will be acted upon.

In case of any questions, don't hesitate to ask Wrangler (jreznik).
Thank you.

[1] https://fedoraproject.org/wiki/Releases/21/Schedule

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/1


On 2014-07-04T10:47:22+00:00 Hans wrote:

Hi,

Not sure what to do with this bug, all the necessary Xorg bits have long
landed, but the only way to run the Xserver as non-root atm is through
startx from a text console, as all the display-managers are not ready
yet. It might be best to move this to F-22 from a feature pov.

Regards,

Hans

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/2


On 2014-07-04T11:04:37+00:00 Jaroslav wrote:

Hi,
thank you for reply. From a feature and (probably even more) from users pov, it 
makes sense to move it to Fedora 22. I'll make sure all places are correctly 
updated to reflect it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/3


On 2014-07-04T13:28:02+00:00 Andrew wrote:

Is it possible to leave it for F-21 with startx only? I know I'm a
minority here, but that's the way I use. Being done this way it might
help to test Xorg in this mode before enabling it for a broader
audience.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/4


On 2014-07-04T13:39:13+00:00 Hans wrote:

(In reply to Andrew Travneff from comment #4)
> Is it possible to leave it for F-21 with startx only? I know I'm a minority
> here, but that's the way I use. Being done this way it might help to test
> Xorg in this mode before enabling it for a broader audience.

For use with startx it requires a tiny bit of manual configuration
(because otherwise various dm-s would be broken), see:
http://hansdegoede.livejournal.com/14446.html

Other then that all the necessary functionality is there, and there is
no intention to remove it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/5


On 2014-07-04T14:22:12+00:00 Andrew wrote:

Wow, thanks! Just in case, is it planned to make the same thing
available for F-20?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/6


On 2014-07-04T15:25:15+00:00 Hans wrote:

(In reply to Andrew Travneff from comment #6)
> Wow, thanks! Just in case, is it planned to make the same thing available
> for F-20?

No.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/7


On 2014-10-20T15:17:12+00:00 Petr wrote:

Change moved to F22, so I'm setting the relnotes flag to - for F21.

Reply at:

[Touch-packages] [Bug 1727687] Re: systemd boots system offline ("Breaking ordering cycle by deleting job network.target/stop")

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727687

Title:
  systemd boots system offline ("Breaking ordering cycle by deleting job
  network.target/stop")

Status in systemd package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Install LTSP server (dnsmasq as proxy DHCP and tftp; NBD, SSH)
  3. Reboot.
  4. Boot system

  Expected results:
  * system boots to online 

  Actual results:
  * system boots offline; it's a security vulnerability as denial of service

  
  Interesting messages from syslog:

  
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found ordering 
cycle on network-online.target/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
network.target/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
NetworkManager.service/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
basic.target/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
paths.target/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
cups.path/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
sysinit.target/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
nbd-client.service/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on 
network-online.target/stop
  Oct 19 15:25:56 server systemd[1]: network-online.target: Breaking ordering 
cycle by deleting job network.target/stop
  Oct 19 15:25:56 server systemd[1]: network.target: Job network.target/stop 
deleted to break ordering cycle starting with network-online.target/stop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Oct 26 13:50:49 2017
  InstallationDate: Installed on 2016-04-21 (552 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=26069a01-c072-4021-83c5-f6df23dc51d5 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727687/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

[Seth Arnold]

Hello Kevin, I don't want to step on Colin's toes here, but I couldn't
sort out anything from the logs or files so far. I've had success before
with perf to grab call graph information. The usual process is along the
lines of:

- enable the ddebs.ubuntu.com repository to get access to debug symbols:
https://wiki.ubuntu.com/Debug%20Symbol%20Packages

- install packages openssh-server-dbgsym libc6-dbgsym .. as needed

- Record perf results during testing with something like:
  sudo perf record -e syscalls:sys_enter_socket -R -a --call-graph dwarf sleep 
20

- test

- Check results with something like:
  sudo perf script


With luck this will spit out the function names of the call chain at the time 
of the socket() syscall that is being killed (probably alongside a lot of 
unrelated instances -- it's possible to tune the perf line to narrow it down if 
necessary).

I hope this helps,
Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1690485

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 66002] Re: entering 'reboot' at the rescue console brings up gdm

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=463728.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-09-24T09:43:15+00:00 Hans wrote:

Description of problem:
When the fsck of a network based blockdevice (nbd/iscsi) fails, the netfs 
initscript will drop the user to a root shell to repair things and then issue
"shutdown -r now"

upstart seems to try to continue entering the runlevel it was busy with
entering despite the reboot command being given.

While at the same time (in parallel??) starting a runlevel switch to the
new (reboot) runlevel.

Most noticeably here is that upstart spews messages like:
-process tty1 died, respawning 
-process prefdm died, respawning
(not the exact text but like that)

While its busy shutting down services for the reboot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/11


On 2008-09-24T14:01:05+00:00 Bill wrote:

Hm, looking at a tty, for example:

start on stopped rc2
start on stopped rc3
start on stopped rc4
start on started prefdm

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

So, it may start quickly (on the stop of the runlevel) but then stop
again (on the start of runlevel 0/1/6)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/12


On 2008-11-26T03:12:22+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 10 
development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/13


On 2009-11-18T08:25:19+00:00 Bug wrote:


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/23


On 2009-12-18T06:25:49+00:00 Bug wrote:


Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/24


** Changed in: upstart (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/66002

Title:
  entering 'reboot' at the rescue console brings up gdm

Status in upstart package in Ubuntu:
  Fix Released
Status in upstart package in Fedora:
  Won't Fix

Bug description:
  Situation: Being dropped to a shell because of a fschck.

  There I say 'reboot' to reboot the machine. Result is that gdm is
  started instead of the machine being rebooted.

  System: Freshly installed edgy from daily 13/10/2006.

To manage notifications about this bug go to:

[Touch-packages] [Bug 284211] Re: [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option

[Bug Watch Updater]

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451027.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-06-12T14:19:07+00:00 Major wrote:

Description of problem:
GTC encapsulation support is unavailable when you choose WPA2 -> PEAP in 
NetworkManager.  Only 
MSCHAP/v2 and CHAP are shown, even though GTC is included in wpa_supplicant.  
The same versions 
of NetworkManager on other distributions includes support for GTC.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.6.7.svn3370.fc8 (Fedora 8)

Steps to Reproduce:
1. Click NetworkManager applet in GNOME
2. Choose a WPA-2 network
3. Choose LEAP
4. GTC is unavailable
  
Actual results:
GTC does not appear as a selection

Expected results:
GTC should appear as a selection

Additional info:
GTC is already included in wpa_supplicant, but is mysteriously missing in 
NetworkManager

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/0


On 2008-08-11T17:56:30+00:00 Dan wrote:

Some of the infrastructure is not there yet, but support for this should
be coming in the future.  Not sure how long.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/1


On 2008-09-23T05:00:15+00:00 S. wrote:

Looking at nm-supplicant-settings-verify.c, taken from 
NetworkManager-0.7.0-0.11.svn4022.fc8.src.rpm, I see:
const char * phase2_allowed[] =   {"auth=PAP", "auth=CHAP", "auth=MSCHAP",
   "auth=MSCHAPV2", "auth=GTC", "auth=OTP",
   "auth=MD5", "auth=TLS", "autheap=MD5",
   "autheap=MSCHAPV2", "autheap=OTP",
   "autheap=GTC", "autheap=TLS", NULL };
But I'm not seeing GTC as an option for PEAP (nor TTLS). The last discussion 
regarding GTC support I'm finding on the networkmanager-list archives is from 
early 2007. Is there more still needed to be done or other configure options 
needed? Willing to help, unsure where to start.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/2


On 2008-11-26T10:51:40+00:00 Bug wrote:


This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/7


On 2009-01-09T06:35:44+00:00 Bug wrote:


Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/284211/comments/15


On 2009-02-18T02:47:39+00:00 James wrote:

This "Bug" (or lack of a feature) is still present in F10.  I think it
was available in on older version, but I'm not sure.

[Touch-packages] [Bug 260918] Re: needed: libv4l and associated application patches (or "gspca stopped working in 2.6.27")

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=456868.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-07-28T09:28:08+00:00 Hans wrote:

Short intro: I'm a long time Linux developer currently working on improving
webcam support in Linux, see:
http://fedoraproject.org/wiki/Features/BetterWebcamSupport

I'm one of the authors of the v4l2 rewrite of the gspca usb webcam driver
framework (which supports more then 100 different cams), this v4l2 rewrite has
been merged into the 2.6.27 kernel and thus will become available in the
official Linux kernel soon.

One of the parts of the v4l2 rewrite has been removing conversion from various
manufacturer cam specific video formats to more normal videoformats from the
drivers, as this really does not belong in kernel space.

As a result of this the gspca subdrivers can generate raw video frames in the
following formats:

#define V4L2_PIX_FMT_SN9C10X  v4l2_fourcc('S', '9', '1', '0') /* SN9C10x
compressed bayer
#define V4L2_PIX_FMT_SPCA501  v4l2_fourcc('S', '5', '0', '1') /* YUYV per line 
#define V4L2_PIX_FMT_SPCA505  v4l2_fourcc('S', '5', '0', '5') /* YYUV per line 
#define V4L2_PIX_FMT_SPCA508  v4l2_fourcc('S', '5', '0', '8') /* YUVY per line 
#define V4L2_PIX_FMT_SPCA561  v4l2_fourcc('S', '5', '6', '1') /* compressed
GBRG bayer
#define V4L2_PIX_FMT_PAC207   v4l2_fourcc('P', '2', '0', '7') /* compressed
BGGR bayer

As we do not want to see each application implement (nor having to implement)
support for these various formats, as we like to have one code base and only
one code base for these formats. A library has been written (with me as the
main author) to convert from these formats to BGR24 or YUV420. For more on this
library see:
http://hansdegoede.livejournal.com/3636.html

The attached patch adds support to the pwlib v4l2 plugin to use this
library if available on the system.

It has also been submitted upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=545108

libv4l has just been build for rawhide, and should show up in the next rawhide
push, in the mean time you can get it from koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57774

###

A note about the patch, the patch is actually quite simple, as libv4l has been
designed for quick porting of existing apps to libv4l, for this reason libv4l
fully mimicks the raw /dev/video interface (and if no conversion is needed and
for non relevant calls like setting ctrl's, passes through all calls
unmodified).

All that the patch does and all that needs to be changed to use libv4l is
replace the relevant xxx calls on /dev/video with v4l2_xxx calls.

I've successfully tested this patch with ekiga and 2 spca561 cams (quite
popular IC, used by both logitech and creative), 2 pac207 cams (another quite
popular IC), 3 SN9C10X cams (also very popular) and 1 spca501 cam. All of which
do not work (unless using gspca version 1) without this patch, as pwlib does
not support their proprietary video formats (and rightfully so).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/0


On 2008-07-28T09:28:08+00:00 Hans wrote:

Created attachment 312759
PATCH: use libv4l in v4l2 plugin, adding support for many cam specific formats

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/1


On 2008-07-29T19:08:36+00:00 Hans wrote:

Note that this patch has just been accepted upstream, see:
http://bugzilla.gnome.org/show_bug.cgi?id=545108

If you want and the CVS ACL's allow it I can push this to rawhide
myself.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/2


On 2008-08-23T07:40:11+00:00 Hans wrote:

Ping!

I really want to see this hit rawhide before we go into a beta freeze,
and as the patch has been accepted upstream I so no reasons for not
putting this in rawhide. If I get no response soon I'll commit it to
rawhide myself (assuming the ACL's will let me).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/3


On 2008-09-19T21:08:37+00:00 Jesse wrote:

Seems it's a bit late for that.  Punting to F10Target.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/7


On 2008-09-20T17:19:12+00:00 Hans wrote:

(In reply to comment #4)
> Seems it's a bit late for that.  Punting to F10Target.

Actually this is long fixed, byt I 

[Touch-packages] [Bug 59981] Re: suspend makes network-manager say eth1 is a wired device

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=442527.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-04-15T11:32:05+00:00 Martin wrote:

Description of problem:
When resuming after suspend to ram, NM tries to connect to a wired connection,
although no cable is plugged in.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.9.1.svn3549.fc9.i386
kernel-2.6.25-0.218.rc8.git7.fc9.i686
hal-0.5.11-0.5.rc2.fc9.i386

How reproducible:
Every time

Steps to Reproduce:
1. Make sure you do not have a cable plugged in and are connected to a wifi 
network
2. Suspend
3. Resume
  
Actual results:
It tries to connect to wired network. Fails, does not show that it is connected
to some network, but is connected to the wifi network (like i can surf).

Expected results:
Should reconnect to the wireless network and show that it is doing so.

Additional info:
I experienced it some time ago. It may be an issue with hal. I'll attach
/var/log/messages output.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/59981/comments/38


On 2008-04-15T11:32:05+00:00 Martin wrote:

Created attachment 302437
messages cutting

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/59981/comments/39


On 2008-05-14T09:28:33+00:00 Bug wrote:

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/59981/comments/41


On 2008-10-28T15:06:38+00:00 Martin wrote:

Probably caused by the network driver in the kernel (via-rhine). Somehow
it thinks that a cable is plugged in to eth0 after suspend to ram.

More information here:
http://www.kerneloops.org/submitresult.php?number=74651 and in the
kernel bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/59981/comments/51


On 2008-11-26T02:12:54+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 10 
development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/59981/comments/52


On 2009-11-18T12:28:23+00:00 Bug wrote:


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/59981/comments/54


On 2009-12-18T06:06:38+00:00 Bug wrote:


Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:

[Touch-packages] [Bug 220014] Re: wrong mail displayed

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=442926.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-04-17T16:24:26+00:00 Need wrote:

This one might be a blocker.

I have a list of e-mail messages, but when I open some of them either in the
preview pane or by double-clicking, I get a different e-mail message.

This is a data loss bug since I may delete the wrong e-mail. Marking severity as
High.

evolution-2.22.1-1.fc9.i386
evolution-data-server-2.22.1-1.fc9.i386

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/0


On 2008-04-17T16:26:33+00:00 Need wrote:

Restarting evolution or e-d-s did not solve the problem.

As a workaround, to hide the problem, I can do the following:
1. Create a new folder
2. Drag all messages to the new folder
3. Drag all the messages from the new folder back to the original folder

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/1


On 2008-04-17T17:17:51+00:00 Milan wrote:

It seems like problem with a summary of the folder. Are there any messages on
the Evolution's console? (In case you run evolution on console and you are able
to reproduce it.)

Maybe it doesn't report problems too loudly. Can you look at Help->Debug Logs
and show all messages, whether you will see there something? I've such a feeling
that it is not stored between sessions, maybe something useful in time of the
issue can be found in ~/.evolution/cache/tmp/mail.log.XX where XX is
some unique generated code for each session.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/2


On 2008-04-17T17:31:38+00:00 Need wrote:

I get one message about a corrupt mbox and a missing From: header.
The messages were kind of off-by-one wrong, so I guess evolution's handling of
missing From: headers needs work..

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/3


On 2008-04-18T07:50:37+00:00 Milan wrote:

I recalled it yesterday, at home. It's because of enabled large file support,
your 32bit machine is not ready for such thing yet, we should disable this
feature until it will be really fixed. I'm sorry for inconvenience, that's my 
fault.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/4


On 2008-04-22T06:12:18+00:00 Need wrote:

I still have the problem.

evolution-2.22.1-1.fc9.i386

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/9


On 2008-04-22T12:30:23+00:00 Milan wrote:

It showed up that the large file support, I was thinking of, is not included in
this evolution release, furthermore, this part is exactly same as in 2.12.x 
version.

For your case, I would like to suggest to close evolution and remove your
summaries, so it will be recreated on next start (it will start significantly
slower, because downloading necessary info from the server about your messages
in each folder. It has some disadvantages too, because some message flags are
stored only in the summary file, and not on the server (or for local accounts
like POP it's stored only locally (the flags of mails). But anyway, it seems
you've broken your summary files already, so probably no other way to fix it.

First of all run "evolution --force-shutdown", so everything evolution related
will be closed.

Then, if you go to ~/.evolution/mail, there are subdirectories for account
types, like "local", "imap" and so on. In each folder you can see some
.ev-summary files, which you can move somewhere else and let evolution rebuild
it on next start. I would recommend to create a backup of whole ~/.evolution
before any tests, so you will be sure you can go back to previous state in case
something goes wrong. Even more, I would like to suggest to remove also .index
and .cmeta files, so those will be regenerated as well.

I'm not aware of any command or UI option to regenerate indexes/summary files,
unfortunately. One more time, do backup of the folder before playing with files.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/220014/comments/11

[Touch-packages] [Bug 238481] Re: openobex-1.3 does not correctly work with non-English chars in phone filesystem

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=430128.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-01-24T17:47:03+00:00 Constantin wrote:

Description of problem:
incorrect work with non-English characters in phone filesystem

Version-Release number of selected component (if applicable):
1.3

How reproducible:

when the phone with non-English language is mounted via obexfs, the non-English
named directories are not accessible


Steps to Reproduce:
1. obexfs -i 
2. cd 
  
Actual results:

Russian directories are not accessible

Expected results:


Additional info:
I have found some patch:
http://www.mail-archive.com/openobex-users@lists.sourceforge.net/msg00587.html

rebuilt rpms from srpm -

and now my Sony Ericsson K700i with Russian language correctly works
with obexfs

The proposition is to include this patch to rpm package

another (later) patch version:
http://www.mail-archive.com/openobex-users@lists.sourceforge.net/msg00595.html
does NOT work correctly (sometimes fusermounted filesystem is not accessible
after directory change)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/238481/comments/0


On 2008-01-24T17:47:03+00:00 Constantin wrote:

Created attachment 292829
this is the patch, I have found

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/238481/comments/1


On 2008-06-06T09:54:31+00:00 Fedora wrote:

openobex-1.3-11.fc8 has been submitted as an update for Fedora 8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/238481/comments/2


On 2008-06-06T22:10:13+00:00 Fedora wrote:

openobex-1.3-11.fc8 has been pushed to the Fedora 8 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openobex'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/F8/FEDORA-2008-5065

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/238481/comments/3


** Changed in: fedora
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libopenobex in Ubuntu.
https://bugs.launchpad.net/bugs/238481

Title:
  openobex-1.3 does not correctly work with non-English chars in phone
  filesystem

Status in libopenobex package in Ubuntu:
  Confirmed
Status in Fedora:
  Fix Released

Bug description:
  When mounting mobile phone via obexfs with non-English language set to 
default in phone, the folders & files with non-English chars are not 
accessible, because of the bug in openobex. I have found a patch, recompile the 
library, and it works now.
  Some months ago i have reported to Red Hat team about this, and now they have 
fixed it in current Fedora.
  But I have switched to Ubuntu Hardy and now I see the same problem.

  Attached file (Red Hat patch) solves the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/238481/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=432963.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-02-15T14:00:30+00:00 Matěj wrote:

Description of problem:
See http://thread.gmane.org/gmane.linux.redhat.fedora.devel/76670

Apparently many people didn't even know about beautiful mechanism of locales,
which is available in Linux. Theory is that if there is nice GUI configuration
mechanism for that, locales might be more used.

KDE has pretty good tool for this, but certainly some GNOME "don't stand in the
way of users doing what they want by forcing them operate your program" could be
useful. I know that there is an option to change language of Gnome session as
whole (which sets LANG variable), but AFAIK it is not possible to change
individual LC_* variables.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/228077/comments/0


On 2008-02-15T14:28:14+00:00 Matthias wrote:

Feature requests like this really need to handled upstream.
FWIW, the control center contains a localization capplet, but it doesn't do
anything right now, therefore it isn't built.
Any solution you come up with here will have the suckiness factor of 'requires
relogin'.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/228077/comments/1


On 2008-02-15T22:03:04+00:00 Matěj wrote:

Done. http://bugzilla.gnome.org/show_bug.cgi?id=516756

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/228077/comments/2


** Changed in: gnome-control-center (Fedora)
   Status: Fix Released => Won't Fix

** Changed in: gnome-control-center (Fedora)
   Importance: Unknown => Low

** Bug watch added: GNOME Bug Tracker #516756
   https://bugzilla.gnome.org/show_bug.cgi?id=516756

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/228077

Title:
  libgtk2 immodules has cedilla disabled in en locales

Status in gnome-control-center:
  Confirmed
Status in GTK+:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Invalid
Status in gnome-control-center package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: libgtk2.0-0

  philsf@philsf-laptop:~$ lsb_release -rd
  Description:  Ubuntu 8.04
  Release:  8.04

  philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0
  libgtk2.0-0:
Installed: 2.12.9-3ubuntu3

  One can't use dead keys to input a c+cedilla in en_US (probably other
  en_* locales). I had this on Gutsy. Now in Hardy, I thought I should
  report, since it's annoying, and the fix is documented.

  Steps to reproduce: 
  - enable deadkeys
  - Open gnome-terminal (or firefox) and enter ' + c 

  What you should get: ç
  What you do get: ć 

  Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ):

  
  Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and 
include ":en" in the cedilla line

  6c6
  < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa" 
  ---
  > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/228077/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown

[Bug Watch Updater]

** Changed in: systemd (Fedora)
   Status: Unknown => Invalid

** Changed in: systemd
   Status: Unknown => Invalid

** Changed in: systemd (Fedora)
   Importance: Unknown => Undecided

** Changed in: systemd
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448259

Title:
  Systemd does not send SIGTERM first on shutdown

Status in systemd:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in systemd package in Debian:
  Fix Released
Status in systemd package in Fedora:
  Invalid

Bug description:
  It has been normal that applications first get the SIGTERM signal
  before SIGKILL on shutdown/reboot in order to successfully finish any
  pending tasks. Now it seem this logic has been changed to something
  else, causing problems to mosh and many others:

  https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982

  SIGTERM  suggestion can be seen here:

  http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8

  I created this error report to find out the correct way for
  applications to fix this problem or to create one fix to systemd,
  bringing back the old "BSD shutdown" functionality.

  This report is for Ubuntu 15.04.

  SRU TEST CASE:
   - Open a terminal, enter some commands, then run "reboot".
   - After a reboot, chances are very high that your bash history does not 
contain your most recently typed commands
   - With the updated package, the bash history should be intact.

  REGRESSION POTENTIAL:
   - The original commit was applied because of an inherent race condition with 
cgroup's release_agent -- in rare corner cases an nspawn container (probably 
also LXC) can miss them. In that case it's possible that you instead get a 90s 
timeout on the unit that is shutting down. But this does not mean data loss, 
just a rare shutdown hang from containers (for the record, I never actually saw 
that hanging with LXC), so I think it's a good trade-off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1716976] Re: DNS resolver silently switches to an unknown DNS server

[gpothier]

** Attachment added: "Wireshark capture of successful resolution, showing IPv6 
stuff happening"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4997138/+files/Screenshot%20from%202017-10-26%2018-36-23.png

** Summary changed:

- DNS resolver silently switches to an unknown DNS server
+ DNS resolver mixes IPv6 and IPv4 caches

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1716976

Title:
  DNS resolver mixes IPv6 and IPv4 caches

Status in systemd package in Ubuntu:
  New

Bug description:
  In our network we have a DNS server that resolves some names to local
  addresses, while the same names are resolved to our public IP when
  public DNSs are used. For instance (using fictitious names and IPs),
  xyz.mydomain.com resolves to the public IP 65.254.242.180 when using
  an external DNS server, but resolves to 192.168.0.14 when using our
  internal DNS server (which all our computers are told to use via
  DHCP).

  This used to work fine until a somewhat recent update in Ubuntu 17.10.
  Now, xyz.domain.com almost always resolves to the public IP instead of
  the internal IP. Interestingly, restarting the systemd-resolved
  service fixes the problem for a while (from a few seconds to a few
  minutes). Right after restarting the service, the dig command reports
  the expected internal IP, but after a while it gets back to reporting
  the public IP. Forcing the dig command to query our DNS server instead
  of the local resolver returns the correct IP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:34:50 2017
  InstallationDate: Installed on 2015-01-23 (963 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1716976] Re: DNS resolver silently switches to an unknown DNS server

[gpothier]

This is still happening with 17.10 final. I have been digging a bit and
found something that makes me think that this is a caching / IPv6 issue.
Attached is the screenshot of a Wireshark capture of the DNS packets on
all interfaces on the affected machine (the IP address of the machine is
192.168.0.154).

When querying a hostname that should be resolved to a local network address (in 
this case odoo.caligrafix.cl), the resolver makes two requests to our local DNS 
server 192.168.0.2 (and not to any external DNS server, as I first thought): 
1. The request for odoo.caligrafix.cl
2. A request for o3.caligrafix.cl.

The second request is made before receiving the response to the first
request. This second request can be explained by the fact that outside
of our network, the name odoo.caligrafix.cl resolves to a CNAME
o3.caligrafix.cl, and for some reason the resolver uses this cached
information instead of waiting for the result of the first request.

The response to the first request, which correctly indicates the
expected local network address, seems to be discarded, and the result of
subsequent requests that resolves to our public address trough a chain
of CNAMES, is used instead.

The funny thing is that after flushing the resolver's cache, the
resolver also makes two requests to our local DNS server, but both with
the name odoo.caligrafix.cl, and gets the correct answer. But then it
makes a request for the  (IPv6) record, and gets the chain the CNAME
records that lead to our public IP. So it seems that somehow the IPv6
and IPv4 caches get mixed up afterwards.

Although I guess I could (and will attempt to) mitigate the issue by 
configuring the  record differently on our DNS server, I think the current 
behavior of the resolver is incorrect, as it uses cached info for an IPv6 
record when querying an IPv4 record.
 


** Attachment added: "Wireshark capture of failed resolution"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4997137/+files/Screenshot%20from%202017-10-26%2018-22-20.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1716976

Title:
  DNS resolver mixes IPv6 and IPv4 caches

Status in systemd package in Ubuntu:
  New

Bug description:
  In our network we have a DNS server that resolves some names to local
  addresses, while the same names are resolved to our public IP when
  public DNSs are used. For instance (using fictitious names and IPs),
  xyz.mydomain.com resolves to the public IP 65.254.242.180 when using
  an external DNS server, but resolves to 192.168.0.14 when using our
  internal DNS server (which all our computers are told to use via
  DHCP).

  This used to work fine until a somewhat recent update in Ubuntu 17.10.
  Now, xyz.domain.com almost always resolves to the public IP instead of
  the internal IP. Interestingly, restarting the systemd-resolved
  service fixes the problem for a while (from a few seconds to a few
  minutes). Right after restarting the service, the dig command reports
  the expected internal IP, but after a while it gets back to reporting
  the public IP. Forcing the dig command to query our DNS server instead
  of the local resolver returns the correct IP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:34:50 2017
  InstallationDate: Installed on 2015-01-23 (963 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Ukraine] [Bug 1727276] [NEW] When using Ukrainian input it looks like alt is always pressed

[Ihor Romanyshyn]

I'm using default win+space. And this problem happens only sometimes.

On Oct 26, 2017 21:51, "Vitaliy Kulikov"  wrote:

could you change keyboard layout switch combination to something without
ALT (ctrl+shift) ? notify us about behavior.

On Oct 25, 2017 13:42, "Launchpad Bug Tracker" <1727...@bugs.launchpad.net>
wrote:

> You have been subscribed to a public bug by Ihor Romanyshyn (iromanyshyn):
>
> Hi people! I have a BIG problem with text input in Ukrainian language.
> When i switch input from English to Ukrainian or use dot it looks like
> [alt] is pressed continuously after that so if I type some text in
> Ukrainian i getting lot of ©®ёэ§²•ъ»«ы (special symbols) instead of my
> text. My keyboard is Ok, it's new Ubuntu 17.10 problem... To temporarily
> input text as normal I need always press [alt] before input any new
> portion of text in Ukrainian, this is frustrating and makes me feel bad.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: keyboard-configuration 1.166ubuntu7
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Oct 25 13:20:00 2017
> InstallationDate: Installed on 2017-10-19 (5 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
> Keyboard:
>  XKBLAYOUT=us
>  BACKSPACE=guess
> PackageArchitecture: all
> ProcEnviron:
>  TERM=xterm-256color
>  PATH=(custom, no user)
>  XDG_RUNTIME_DIR=
>  LANG=uk_UA.UTF-8
>  SHELL=/bin/bash
> SourcePackage: console-setup
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: console-setup (Ubuntu)
>  Importance: Undecided
>  Status: New
>
>
> ** Tags: amd64 apport-bug artful wayland-session
> --
> When using Ukrainian input it looks like alt is always pressed
> https://bugs.launchpad.net/bugs/1727276
> You received this bug notification because you are a member of Користувачі
> Убунту в Україні, which is subscribed to the bug report.
>
> ___
> Mailing list: https://launchpad.net/~ukraine
> Post to : ukra...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ukraine
> More help   : https://help.launchpad.net/ListHelp
>

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1727276

Title:
  When using Ukrainian input it looks like alt is always pressed

Status in console-setup package in Ubuntu:
  New

Bug description:
  Hi people! I have a BIG problem with text input in Ukrainian language.
  When i switch input from English to Ukrainian or use dot it looks like
  [alt] is pressed continuously after that so if I type some text in
  Ukrainian i getting lot of ©®ёэ§²•ъ»«ы (special symbols) instead of my
  text. My keyboard is Ok, it's new Ubuntu 17.10 problem... To
  temporarily input text as normal I need always press [alt] before
  input any new portion of text in Ukrainian, this is frustrating and
  makes me feel bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: keyboard-configuration 1.166ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 13:20:00 2017
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
(20171018)
  Keyboard:
   XKBLAYOUT=us
   BACKSPACE=guess
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+
bug/1727276/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1727276

Title:
  When using Ukrainian input it looks like alt is always pressed

Status in console-setup package in Ubuntu:
  New

Bug description:
  Hi people! I have a BIG problem with text input in Ukrainian language.
  When i switch input from English to Ukrainian or use dot it looks like
  [alt] is pressed continuously after that so if I type some text in
  Ukrainian i getting lot of ©®ёэ§²•ъ»«ы (special symbols) instead of my
  text. My keyboard is Ok, it's new Ubuntu 17.10 problem... To
  temporarily input text as normal I need always press [alt] before
  input any new portion of text in Ukrainian, this is frustrating and
  makes me feel bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: keyboard-configuration 1.166ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Jeremy Soller]

Here is a patch without symbol changes or whitespace changes

** Patch added: "accountsservice_encrypt_home.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4997109/+files/accountsservice_encrypt_home.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1699216

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

[Andreas Hasenack]

Interesting:
Exception in thread "AWT-EventQueue-1" com.jogamp.opengl.GLException: Caught 
GLException: AWT-EventQueue-1: createImpl ARB n/a but required, profile > GL2 
requested (OpenGL >= 3.1). Requested: GLProfile[GL3bc/GL3bc.sw], current: 3.0 
(Compat profile, compat[ES2], FBO, software) - 3.0 Mesa 17.2.2

So something to do with opengl over remote X11 connections. I'll switch
the bug over to wayland, and maybe add a xorg task

** Package changed: openssh (Ubuntu) => wayland (Ubuntu)

** Changed in: wayland (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1726595

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in wayland package in Ubuntu:
  New

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1726595/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 196724] Re: console-kit-daemon crashed with SIGSEGV in vt_thread_start()

[Bug Watch Updater]

** Changed in: consolekit (Fedora)
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to consolekit in Ubuntu.
https://bugs.launchpad.net/bugs/196724

Title:
  console-kit-daemon crashed with SIGSEGV in vt_thread_start()

Status in consolekit package in Ubuntu:
  Fix Released
Status in consolekit source package in Hardy:
  Won't Fix
Status in consolekit package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: consolekit

  Reboot with Hardy updates on 29th Feb.

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Fri Feb 29 01:38:08 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/sbin/console-kit-daemon
  NonfreeKernelModules: cdrom
  Package: consolekit 0.2.3-3ubuntu3
  PackageArchitecture: i386
  ProcCmdline: /usr/sbin/console-kit-daemon
  ProcEnviron:
   
  Signal: 11
  SourcePackage: consolekit
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: console-kit-daemon crashed with SIGSEGV
  Uname: Linux 2.6.24-10-generic i686
  UserGroups:
  SegvAnalysis:
   Segfault happened at: 0xb7dbc44e:call   *0xc(%edx)
   PC (0xb7dbc44e) ok
   source "*0xc(%edx)" (0xc35d0851) not located in a known VMA region (needed 
readable region)!
  SegvReason: reading unknown VMA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/196724/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 218652] Re: CVE-2008-1686: Multiple speex implementations insufficient boundary checks

[Bug Watch Updater]

Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=441239.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-04-07T11:41:09+00:00 Tomas wrote:

Common Vulnerabilities and Exposures assigned an identifier
CVE-2008-1686 to the following vulnerability:

Quoting oCert advisory:

The libfishsound decoder library incorrectly implements the reference speex
decoder from the Speex library, performing insufficient boundary checks on a
header structure read from user input.

A user controlled field in the header structure is used to build a function
pointer. The libfishsound implementation does not check for negative values for
the field, allowing the function pointer to be pointed at an arbitary position
in memory. This allows remote code execution.

Affected version: <= 0.9.0
Fixed version: 0.9.1

Upstream patch in trunk:
http://trac.annodex.net/changeset/3536

References:
http://www.ocert.org/advisories/ocert-2008-2.html
http://lists.xiph.org/pipermail/speex-dev/2008-April/006636.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/0


On 2008-04-07T12:48:20+00:00 Tomas wrote:

oCert-2008-2 was updated to list speex as affected as well:

Additional affected packages:
Speex <= 1.1.6, the reference implementation from which libfishsound is derived.

Current Fedora speex packages are not affected by this problem.  Affected speex
packages are shipped in Red Hat Enterprise Linux 4 and 5.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/1


On 2008-04-07T12:55:52+00:00 Tomas wrote:

For speex, fix first occurred in 1.2.0beta1.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/2


On 2008-04-07T17:51:19+00:00 Tomas wrote:

Some more info in Contrad Parker's blog:

http://blog.kfish.org/2008/04/release-libfishsound-091.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/3


On 2008-04-11T11:24:34+00:00 Tomas wrote:

So far, same issue was identified in following other projects:

- gstreamer-plugins-good-0.10.6
- vorbis-tools-1.1.1 (ogg123)
- sweep-0.9.2
- xine-lib-1.1.11.1
- vlc-0.8.6f (not shipped in Fedora or Red Hat Enterprise Linux)
- SDL_sound-1.0.1
  Fedora packages seems unaffected, as they do not seem to be linked against
  libspeex despite --enable-speex and speex-devel BuildRequires


Reply at: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/4


On 2008-04-11T11:25:53+00:00 Tomas wrote:

So far, fixed upstream in:

- gstreamer-plugins-good
http://webcvs.freedesktop.org/gstreamer/gst-plugins-good/ext/speex/gstspeexdec.c?r1=1.40=1.41

- sweep
http://trac.metadecks.org/changeset/554


Reply at: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/5


On 2008-04-12T17:11:09+00:00 Tomas wrote:

Speex upstream added check in speex_packet_to_header(), so that can address this
problem for all affected apps, that use speex_packet_to_header and check its
return value (all applications seem to do that correctly).  For caller of
speex_packet_to_header that does not check return value, it will reduce problem
to a crash caused by NULL pointer dereference.

Patch applied to speex_packet_to_header():

$ svn diff -c 14701 http://svn.xiph.org/trunk/speex/libspeex/
Index: speex_header.c
===
--- speex_header.c  (revision 14700)
+++ speex_header.c  (revision 14701)
@@ -178,6 +178,13 @@
ENDIAN_SWITCH(le_header->frames_per_packet);
ENDIAN_SWITCH(le_header->extra_headers);

+   if (le_header->mode >= SPEEX_NB_MODES || le_header->mode < 0)
+   {
+  speex_notify("Invalid mode specified in Speex header");
+  speex_free (le_header);
+  return NULL;
+   }
+
if (le_header->nb_channels>2)
   le_header->nb_channels = 2;
if (le_header->nb_channels<1)

$ svn log -r 14701 http://svn.xiph.org/trunk/speex/libspeex/

r14701 | jm | 2008-04-11 05:48:46 +0200 (Fri, 11 Apr 2008) | 5 lines

Patch by kfish that checks for headers with invalid mode numbers. Technically,
it should have been the application's responsability, but many didn't, so
we ended up with security issues. Considering that 

[Touch-packages] [Bug 285831] Re: icon for ms-word file *.doc is "?" instead of ooo-word

[Bug Watch Updater]

Launchpad has imported 27 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=442443.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-04-14T20:16:39+00:00 Orion wrote:

Description of problem:

The .doc files on my desktop (and a newly created test user) are using a ? icon.
 No idea how this gets set or whose fault this might be.  xls files are okay
(show some kind of spreadsheet icon).

Version-Release number of selected component (if applicable):
kdebase-4.0.3-6.fc9.i386

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/0


On 2008-04-14T21:19:32+00:00 Rex wrote:

shared-mime-info should handle mimetypes, etc, now.

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/1


On 2008-04-14T21:22:19+00:00 Rex wrote:

I take it back, you actually need an app installed that claims to be able to
handle that mimetype, that provides an icon.

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/2


On 2008-04-14T21:25:12+00:00 Kevin wrote:

So I guess KWord is only registering it with the old KDE 3 system? KOffice 
probably needs to be fixed to use shared-mime-info.

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/3


On 2008-04-14T21:28:18+00:00 Rex wrote:

ignore me, for now, I'll keep digging.  :)

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/4


On 2008-04-14T21:29:58+00:00 Orion wrote:

Should pick of OO too:


/usr/share/applications/openoffice.org-1.9-writer.desktop:
MimeType=application/vnd.oasis.opendocument.text;application/vnd.oasis.opendocument.text-template;application/vnd.oasis.opendocument.text-web;application/vnd.oasis.opendocument.text-master;application/vnd.sun.xml.writer;application/vnd.sun.xml.writer.template;application/vnd.sun.xml.writer.global;application/vnd.stardivision.writer;application/msword;application/vnd.ms-word;application/x-doc;application/rtf;application/vnd.wordperfect;application/wordperfect
Icon=openofficeorg-writer


Icons are here:
/usr/share/icons/hicolor/16x16/apps/openofficeorg-writer.png
/usr/share/icons/hicolor/32x32/apps/openofficeorg-writer.png
/usr/share/icons/hicolor/48x48/apps/openofficeorg-writer.png
/usr/share/icons/locolor/16x16/apps/openofficeorg-writer.png
/usr/share/icons/locolor/32x32/apps/openofficeorg-writer.png

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/5


On 2008-04-14T21:31:49+00:00 Orion wrote:

FYI - I don't have koffice.

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/6


On 2008-04-14T21:34:03+00:00 Kevin wrote:

The file type icons don't come from the application (in other words, that 
Icon=openofficeorg-writer is irrelevant). An icon matching the name of the MIME 
type is searched.

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/7


On 2008-04-14T21:42:13+00:00 Orion wrote:

So it should be using:

/usr/share/icons/oxygen/32x32/mimetypes/application-vnd.ms-word.png

?

Maybe a naming/alias issue:

  




  


gnome has:

/usr/share/icons/gnome/16x16/mimetypes/gnome-mime-application-msword.png

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/8


On 2008-04-15T00:01:30+00:00 Rex wrote:

I tried various things here, but couldn't get the mimetype to match/use the
icon.  Something is amiss, but I think at least it's partially some goofy and/or
duplicated parts in the application/msword.xml mimetype.

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-
info/+bug/285831/comments/9


On 2008-05-14T09:26:25+00:00 Bug wrote:

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/shared-mime-

[Touch-packages] [Bug 1681910] Re: gnome-terminal constantly logs "Unable to load blank_cursor from the cursor theme" under gnome/wayland

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1681910

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Under GNOME/Wayland, regardless of cursor theme (I'm using 'DMZ-
  White', but confirmed with 'Adwaita'), whenever the terminal obtains
  focus and the user starts entering input, gnome-terminal will generate
  two log entries:

  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme
  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme

  This seems to be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417490

  and related to:
  https://bugzilla.gnome.org/show_bug.cgi?id=775217

  (though in Ubuntu 17.04 the log doesn't contain 'gdkcursor-
  wayland.c:170' like in the gnome bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1681910/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 187832] Re: CD drive spins at maximum speed when playing CD

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=431178.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-02-01T10:32:31+00:00 Mario wrote:

Description of problem:

Playing an audio CD on my laptop (HP DV8291ea) using a GStreamer based
application (like gst-launch, totem, rhythmbox) causes the CD drive to run at
full speed. This is disturbing both for the noise and for the vibrations. Using
other apps like Amarok does not push the drive to the limit.

I have tracked down the problem to be either the gstcdparanoiasrc plugin or the
cdparanoia library, but had not time to read the code.

You can test it easily by doing:

gst-launch cdparanoiasrc ! alsasink

and then Amarok and comparing the two.

There is a similar bug report in the Ubuntu launchpad, so this is not Fedora
specific:

https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/187832

Version-Release number of selected component (if applicable):

[neugens@nirvana ~]$ rpm -q gstreamer-plugins-base ; rpm -q cdparanoia
gstreamer-plugins-base-0.10.15-1.fc8
cdparanoia-alpha9.8-27.2

How reproducible:

Always

Steps to Reproduce:
1. Insert you favorite CD
2. run a GStreamer based application, or use gst-launch like:
   gst-launch cdparanoiasrc ! alsasink
3. Listen to the drive spinning at fool (not a typo) speed
  
Actual results:

The CD drive spins at full speed

Expected results:

To play an audio CD, a read speed of 1x is the only one needed.

Additional info:

It seems to happen only with GStreamer; cdparanoiasrc has a "read-speed"
property, but it seems not to be honored. That is, this command:

gst-launch cdparanoiasrc read-speed=24 ! alsasink

and this command:

gst-launch cdparanoiasrc read-speed=1 ! alsasink

have the same effect.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/2


On 2008-02-01T10:39:40+00:00 Mario wrote:

Thinking about it, the fact that read-speed is not honored, may hide a bug in
cdparanoia and not in gstreamer itself... I'll try to give a look at the code
tonight. I don't think it's an high priority bug, but it is quite disturbing if
you plan to use your Linux box as media center (or.. well, if you use your
laptop as a huge cdplayer like I do :).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/3


On 2008-02-02T19:35:25+00:00 Mario wrote:

After further analysis I think that this is in fact a bug against
cdparanoia.

I've not gone through accurate testing yet, but I think that the problem is in
the function "scsi_init_drive" (see
cdparanoia-III-alpha9.8/interface/scsi_interface.c:1612). Apparently, setting
drive speed is not supported by cdparanoia on SCSI devices...


Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/4


On 2008-02-02T20:27:58+00:00 Mario wrote:

I've attached two patches that fix the problem for me. The first adds speed
setting capability via ioctl to cdparanoia (apply to cdparanoia-alpha9.8-27.2),
the other sets the default speed to 4 in gstreamer-plugin-base (apply to 
gstreamer-plugins-base-0.10.15-1). These need more testings as they may kill
your cddrive, so use with care!! I have the patched spec files for rpm also if
you need these.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/5


On 2008-02-02T20:30:25+00:00 Mario wrote:

Created attachment 293804
Add set_speed to scsi_interface.c for cdparanoia-III-alpha9.8

Apply this patch to cdparanoia-alpha9.8-27.2.src.rpm

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/6


On 2008-02-02T20:31:51+00:00 Mario wrote:

Created attachment 293805
Sets cd drive speed to default to 4 (as xine also does) instead of the default

Apply this patch to gstreamer-plugins-base-0.10.15-1.fc8.src.rpm

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/7


On 2008-03-04T20:59:42+00:00 Adam wrote:

These look plausible to me, and didn't get a clear nak from the cdparanoia
maintainer.  Building for rawhide now.  Can you test them from rawhide, or
should I push F8 update candidates too?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/187832/comments/9

[Touch-packages] [Bug 174292] Re: Audio volume control keys control microphone volume instead of PCM volume

[Bug Watch Updater]

** Changed in: control-center (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-base0.10 in
Ubuntu.
https://bugs.launchpad.net/bugs/174292

Title:
  Audio volume control keys control microphone volume instead of PCM
  volume

Status in GStreamer:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gst-plugins-base0.10 package in Ubuntu:
  Fix Released
Status in control-center package in Fedora:
  Fix Released

Bug description:
  When pressing "Volume up" and "Volume button" buttons on the keyboard,
  the microphone's volume level is changing, instead of PCM volume
  level. Volume Applet is also displaying microphone's volume level,
  instead of pcm volume level. This is on a ThinkPad X61

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/174292/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 347303] Re: ENV{TZ} and strftime in perl not working

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=172396.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2005-11-03T19:02:30+00:00 Jason wrote:

Description of problem:

This program should print out 2 different timestamps :
---
#!/usr/bin/perl
use POSIX ;
$t = time();
$ENV{'TZ'}="US/Eastern";
$east = scalar( localtime( $t ));
$ENV{'TZ'}="US/Western";
$west = scalar( localtime( $t ));
print $east,"\n", $west,"\n";
---

But it does not: 
$ ./tz.pl
Thu Nov  3 13:54:04 2005
Thu Nov  3 13:54:04 2005

This is because when PERL is compiled with multi-threading enabled, it uses 
localtime_r, which does not call 'tzset', contrary to the documentation
of localtime(3), which does call 'tzset'. 

This is an upstream perl bug :
26136: localtime(3) calls tzset(3), but localtime_r(3) may not. 
  ( http://rt.perl.org/rt3/Ticket/Display.html?id=26136 )

-- Additional comment from t...@redhat.com on 2005-06-22 05:22 EST --
>From User-Agent: XML-RPC

Analyzed the problem and tracked down its cause and also got a workaround.
(Thanks go to Bill Nottingham and Jakub Jelinek for help on this). To get
the original (pre-perl-5.8), you should declare "use POSIX qw(tzset);" at
the start of your script (with other use clauses) and instead of calling
"localtime" call "tzset; localtime" or after each $ENV{TZ} = assignment
call tzset; this should make the script behave as expected. We'll try and
consult perl upstream about this behaviour in the meantime and if the
proposed workaround is not good enough, we'll see if this can be corrected
in the perl package itself.

--- Additional comment from Issue Tracker (t...@redhat.com) on 2005-06-22
05:22 EST

Actually, Pete Rockai found the solution; basically, glibc caches

the timezone. Given their example script, what they need to do is

do an explicit tzset() after setting the environment variable.

i.e.:
/usr/bin/perl -e 'use POSIX qw(tzset); my $t = time; print "$t ", scalar
localtime($t), "\n"; $ENV{TZ} = "Japan"; tzset; my $t = time; print
"$t ", scalar localtime($t), "\n";'

The reason this changed between perl-5.6.x and perl-5.8 is
probably because perl switched to using localtime_r (the thread-safe
version), which doesn't reset the timezone automatically.

What we'd recommend is that they fix their code to explicitly
set the timezone; we can see about having upstream perl change
its behavior to automatically do the tzset on calls to localtime(),
but we don't want to break compatibility with upstream by either
doing it ourselves, or switching perl back to using localtime
instead of localtime_r.

Bill

-- Additional comment from jvd...@redhat.com on 2005-11-02 22:50 EST --
A fix for this issue has been developed, and appended as a patch to the
upstream perl bug that was raised on this issue :
26136: localtime(3) calls tzset(3), but localtime_r(3) may not. 
  ( http://rt.perl.org/rt3/Ticket/Display.html?id=26136 )

If the upstream PERL developers agree to accept this patch, then I will
submit it to our PERL distribution.

The patch detects this problem during the Configure phase, and if it was
detected, and perl is being built multi-threaded (localtime_r is used),
will insert a tzset call before any localtime_r call .

The downside of this fix is that glibc uses mutex locking in the tzset call, 
so there would be a performance hit and multi-threaded perl programs would 
experience synchronisation around their localtime calls ( thankfully, 
genuinely multi-threaded perl programs are few and far between, and no 
other impact other than a performance hit would result from this fix ).

-- Additional comment from jvd...@redhat.com on 2005-11-03 13:47 EST --
OK, I've had some positive feedback on the patch from the perl5-porters mailing
list, but as yet, no response from the perl upstream maintainers.
I'm going to submit the patch to FC-5's perl-5.8.7 release, and if all goes
well, and the upstream maintainers do accept it, I'll apply it to a future
RHEL-4 release ( probably not U3 at this late stage ).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/347303/comments/0


On 2005-11-03T19:04:36+00:00 Jason wrote:

This bug is fixed in perl-5.8.7-0.7.fc5 .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/347303/comments/1


On 2006-10-01T23:32:22+00:00 Robin wrote:

assigning to rnorw...@redhat.com

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/347303/comments/2


** Changed in: perl (Fedora)
   Importance: Unknown => Medium

** Bug watch added: rt.perl.org/rt3/ #26136
   

[Touch-packages] [Bug 1727850] Re: systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Seth Forshee]

>From journal.txt in the adt artifacts:


Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Main process exited, 
code=exited, status=1/FAILURE
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Unit entered failed 
state.
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Failed with result 
'exit-code'.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727850

Title:
  systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727850] Re: systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Seth Forshee]

When I run the systemd tests locally using autopkgtest I cannot
reproduce this failure.

** Tags removed: kernel-adt-failure
** Tags added: kernel-adt-failure-hwe-edge-4.13

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727850

Title:
  systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727850] Re: systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Seth Forshee]

boot-smoke test fails:

checking that there are no running jobs
FAIL: expected: '' actual: '550 lightdm.service start running'

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727850

Title:
  systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp